User interfaces having a collection of complications

ABSTRACT

The present disclosure generally relates to context-specific user interfaces. In particular, the present disclosure relates to an electronic device that includes a user interface having a collection of complications. In some embodiments, a watch user interface is displayed on a display, the watch user interface including an analog clock face area and one or more complications having metrics related to data from an application. In some embodiments, one of the complications is replaced with another complication in response to a sequence of one or more inputs that correspond to a request to add a complication to the watch face.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 62/668,041, titled “CONTEXT-SPECIFIC USER INTERFACES,” filedMay 7, 2018, U.S. Provisional Patent Application Ser. No. 62/679,941,titled “CONTEXT-SPECIFIC USER INTERFACES,” filed Jun. 3, 2018, and U.S.Provisional Patent Application Ser. No. 62/725,215, titled“CONTEXT-SPECIFIC USER INTERFACES,” filed Aug. 30, 2018. The contents ofthese applications are hereby incorporated by reference in theirentirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for context-specific userinterfaces.

BACKGROUND

Portable multifunction devices allow users to concurrently accessinformation from a variety of applications and data sources on areduced-size device they can keep with them throughout the day in avariety of contexts (e.g., at work, at home, while traveling, etc.).

BRIEF SUMMARY

However, as context changes, the types and quantity of information auser may wish to view can also change. Thus, it is a challenge toprovide an efficient interface that displays relevant information to auser throughout the day. For example, a user may normally wish to knowthe current temperature throughout the day but at certain times, wouldlike to have more detailed weather information (e.g., forecasted highand low temperatures). A widget dedicated to displaying detailed weatherinformation would provide irrelevant information (e.g., high and lowtemperature) most of the day, taking up space that could be used toprovide additional relevant information to the user (e.g., informationfrom different applications). This is a particular concern for portabledevices with reduced-size interfaces.

Moreover, users rely on portable multifunction devices for keeping time,and increasingly for performing a variety of other operations includingrunning software applications. However, some techniques for providingcontext-specific user interfaces (e.g., for keeping time and/or otheroperations) are generally cumbersome and inefficient. For example, someexisting techniques use a complex and time-consuming user interface,which can include multiple key presses or keystrokes. Existingtechniques require more time than necessary, wasting user time anddevice energy. This latter consideration is particularly important inbattery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods for context-specific user interfaces.Such methods and interfaces optionally complement or replace othermethods for context-specific user interfaces. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges and reduce the number of unnecessary,extraneous, and/or repetitive received inputs required to accessinformation.

In some embodiments, a method is described. The method comprises: at anelectronic device with a display, displaying a watch user interface onthe display; the watch user interface includes: a first graphical objectat a first location in a sequence of locations on the display; and asecond graphical object at a last location in the sequence of locationson the display. The method further includes, while displaying the watchuser interface on the display: detecting a first user input; and inresponse to detecting the first user input: ceasing to display the firstgraphical object at the first location in the sequence of definedlocations on the display; ceasing to display the second graphical objectat the last location in the sequence of defined locations on thedisplay; displaying the second graphical object at the first location inthe sequence of locations on the display; and displaying the firstgraphical object at a second location in the sequence of locations onthe display.

In some embodiments, a non-transitory computer readable storage mediumis described. The non-transitory computer readable storage medium storesone or more programs configured to be executed by one or more processorsof an electronic device with a display. The one or more programs includeinstructions for: displaying a watch user interface on the display; hewatch user interface including: a first graphical object at a firstlocation in a sequence of locations on the display; and a secondgraphical object at a last location in the sequence of locations on thedisplay; while displaying the watch user interface on the display:detecting a first user input; and in response to detecting the firstuser input: ceasing to display the first graphical object at the firstlocation in the sequence of defined locations on the display; ceasing todisplay the second graphical object at the last location in the sequenceof defined locations on the display; displaying the second graphicalobject at the first location in the sequence of locations on thedisplay; and displaying the first graphical object at a second locationin the sequence of locations on the display.

In some embodiments, a transitory computer readable storage medium isdescribed. The transitory computer readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display The one or more programs includesinstructions for: displaying a watch user interface on the display; thewatch user interface including: a first graphical object at a firstlocation in a sequence of locations on the display; and a secondgraphical object at a last location in the sequence of locations on thedisplay; while displaying the watch user interface on the display:detecting a first user input; and in response to detecting the firstuser input: ceasing to display the first graphical object at the firstlocation in the sequence of defined locations on the display; ceasing todisplay the second graphical object at the last location in the sequenceof defined locations on the display; displaying the second graphicalobject at the first location in the sequence of locations on thedisplay; and displaying the first graphical object at a second locationin the sequence of locations on the display.

In some embodiments, an electronic device is described. The electronicdevice comprises: a display; one or more processors; and memory storingone or more programs configured to be executed by the one or moreprocessors. The one or more programs include instructions for:displaying a watch user interface on the display; the watch userinterface including: a first graphical object at a first location in asequence of locations on the display; and a second graphical object at alast location in the sequence of locations on the display; whiledisplaying the watch user interface on the display: detecting a firstuser input; and in response to detecting the first user input: ceasingto display the first graphical object at the first location in thesequence of defined locations on the display; ceasing to display thesecond graphical object at the last location in the sequence of definedlocations on the display; displaying the second graphical object at thefirst location in the sequence of locations on the display; anddisplaying the first graphical object at a second location in thesequence of locations on the display.

In some embodiments, an electronic device is described. The electronicdevice comprises means for displaying a watch user interface on thedisplay. The watch user interface includes: a first graphical object ata first location in a sequence of locations on the display; and a secondgraphical object at a last location in the sequence of locations on thedisplay. The electronic device further comprises, while displaying thewatch user interface on the display: means for detecting a first userinput; and responsive to detecting the first user input: means forceasing to display the first graphical object at the first location inthe sequence of defined locations on the display; means for ceasing todisplay the second graphical object at the last location in the sequenceof defined locations on the display; means for displaying the secondgraphical object at the first location in the sequence of locations onthe display; and means for displaying the first graphical object at asecond location in the sequence of locations on the display.

In some embodiments, a method is described. The method comprises: at anelectronic device with a display, displaying a watch user interface onthe display at a first time; the watch user interface at the first timeincludes: a first clock hand in a first position overlaid on abackground, the background having a first graphical characteristic atthe first time that is determined based on the first position of thefirst clock hand; and displaying the watch user interface on the displayat a second time after the first time; the watch user interface at thesecond time includes: the first clock hand in a second position overlaidon the background, the background having a second graphicalcharacteristic at the second time that is determined based on the secondposition of the first clock hand.

In some embodiments, a transitory computer-readable storage medium isdescribed. The transitory computer-readable medium stores one or moreprograms configured to be executed by one or more processors of anelectronic device with a display. The one or more programs includeinstructions for: displaying a watch user interface on the display at afirst time; the watch user interface at the first time includes: a firstclock hand in a first position overlaid on a background, the backgroundhaving a first graphical characteristic at the first time that isdetermined based on the first position of the first clock hand; anddisplaying the watch user interface on the display at a second timeafter the first time; the watch user interface at the second timeincludes: the first clock hand in a second position overlaid on thebackground, the background having a second graphical characteristic atthe second time that is determined based on the second position of thefirst clock hand.

In some embodiments, a non-transitory computer-readable storage mediumis described. The non-transitory computer-readable storage medium storesone or more programs configured to be executed by one or more processorsof an electronic device with a display. The one or more programs includeinstructions for: displaying a watch user interface on the display at afirst time; the watch user interface at the first time including: afirst clock hand in a first position overlaid on a background, thebackground having a first graphical characteristic at the first timethat is determined based on the first position of the first clock hand;and displaying the watch user interface on the display at a second timeafter the first time; the watch user interface at the second timeincluding: the first clock hand in a second position overlaid on thebackground, the background having a second graphical characteristic atthe second time that is determined based on the second position of thefirst clock hand.

In some embodiments, an electronic device is described. The electronicdevice comprises: a display; one or more processors; and memory storingone or more programs configured to be executed by the one or moreprocessors. The one or more programs include instructions for:displaying a watch user interface on the display at a first time; thewatch user interface at the first time including: a first clock hand ina first position overlaid on a background, the background having a firstgraphical characteristic at the first time that is determined based onthe first position of the first clock hand; and displaying the watchuser interface on the display at a second time after the first time; thewatch user interface at the second time including: the first clock handin a second position overlaid on the background, the background having asecond graphical characteristic at the second time that is determinedbased on the second position of the first clock hand.

In some embodiments, an electronic device is described. The electronicdevice comprises: a display; a means for displaying a watch userinterface on the display at a first time; the watch user interface atthe first time including: a first clock hand in a first positionoverlaid on a background, the background having a first graphicalcharacteristic at the first time that is determined based on the firstposition of the first clock hand; and a means for displaying the watchuser interface on the display at a second time after the first time; thewatch user interface at the second time including: the first clock handin a second position overlaid on the background, the background having asecond graphical characteristic at the second time that is determinedbased on the second position of the first clock hand.

In some embodiments, a method is described. The method comprises: at anelectronic device with a display: displaying a watch user interface onthe display; the watch user interface includes: a first complicationthat includes at least a first metric related to data from a firstapplication and a second metric related to data from the firstapplication; a second complication that includes at least a third metricrelated to data from a second application and a fourth metric related todata from the second application; and a third complication that includesat least a fifth metric related to data from a third application and asixth metric related to data from the third application; detecting asequence of one or more inputs that corresponds to a request to add afourth complication to the watch user interface, wherein the fourthcomplication includes at least a seventh metric related to data from afourth application and an eighth metric related to data from the fourthapplication; and in response to detecting the sequence of one or moreinputs: in accordance with a determination that the sequence of one ormore inputs corresponds to a request to replace the first complication,replacing the first complication with the fourth complication; inaccordance with a determination that the sequence of one or more inputscorresponds to a request to replace the second complication, replacingthe second complication with the fourth complication; and in accordancewith a determination that the sequence of one or more inputs correspondsto a request to replace the third complication, replacing the thirdcomplication with the fourth complication.

In some embodiments, a transitory computer-readable storage medium isdescribed. The transitory computer-readable medium stores one or moreprograms configured to be executed by one or more processors of anelectronic device with a display. The one or more programs includeinstructions for: displaying a watch user interface on the display; thewatch user interface including: a first complication that includes atleast a first metric related to data from a first application and asecond metric related to data from the first application; a secondcomplication that includes at least a third metric related to data froma second application and a fourth metric related to data from the secondapplication; and a third complication that includes at least a fifthmetric related to data from a third application and a sixth metricrelated to data from the third application; detecting a sequence of oneor more inputs that corresponds to a request to add a fourthcomplication to the watch user interface, wherein the fourthcomplication includes at least a seventh metric related to data from afourth application and an eighth metric related to data from the fourthapplication; and in response to detecting the sequence of one or moreinputs: in accordance with a determination that the sequence of one ormore inputs corresponds to a request to replace the first complication,replacing the first complication with the fourth complication; inaccordance with a determination that the sequence of one or more inputscorresponds to a request to replace the second complication, replacingthe second complication with the fourth complication; and in accordancewith a determination that the sequence of one or more inputs correspondsto a request to replace the third complication, replacing the thirdcomplication with the fourth complication.

In some embodiments, a non-transitory computer-readable storage mediumis described. The non-transitory computer-readable storage medium storesone or more programs configured to be executed by one or more processorsof an electronic device with a display The one or more programs includeinstructions for: displaying a watch user interface on the display; thewatch user interface including: a first complication that includes atleast a first metric related to data from a first application and asecond metric related to data from the first application; a secondcomplication that includes at least a third metric related to data froma second application and a fourth metric related to data from the secondapplication; and a third complication that includes at least a fifthmetric related to data from a third application and a sixth metricrelated to data from the third application; detecting a sequence of oneor more inputs that corresponds to a request to add a fourthcomplication to the watch user interface, wherein the fourthcomplication includes at least a seventh metric related to data from afourth application and an eighth metric related to data from the fourthapplication; and in response to detecting the sequence of one or moreinputs: in accordance with a determination that the sequence of one ormore inputs corresponds to a request to replace the first complication,replacing the first complication with the fourth complication; inaccordance with a determination that the sequence of one or more inputscorresponds to a request to replace the second complication, replacingthe second complication with the fourth complication; and in accordancewith a determination that the sequence of one or more inputs correspondsto a request to replace the third complication, replacing the thirdcomplication with the fourth complication.

In some embodiments, an electronic device is described. The electronicdevice comprises: a display; one or more processors; and memory storingone or more programs configured to be executed by the one or moreprocessors. The one or more programs include instructions for:displaying a watch user interface on the display; the watch userinterface including: a first complication that includes at least a firstmetric related to data from a first application and a second metricrelated to data from the first application; a second complication thatincludes at least a third metric related to data from a secondapplication and a fourth metric related to data from the secondapplication; and a third complication that includes at least a fifthmetric related to data from a third application and a sixth metricrelated to data from the third application; detecting a sequence of oneor more inputs that corresponds to a request to add a fourthcomplication to the watch user interface, wherein the fourthcomplication includes at least a seventh metric related to data from afourth application and an eighth metric related to data from the fourthapplication; and in response to detecting the sequence of one or moreinputs: in accordance with a determination that the sequence of one ormore inputs corresponds to a request to replace the first complication,replacing the first complication with the fourth complication; inaccordance with a determination that the sequence of one or more inputscorresponds to a request to replace the second complication, replacingthe second complication with the fourth complication; and in accordancewith a determination that the sequence of one or more inputs correspondsto a request to replace the third complication, replacing the thirdcomplication with the fourth complication.

In some embodiments, an electronic device is described. The electronicdevice comprises: a display; a means for displaying a watch userinterface on the display; the watch user interface including: a firstcomplication that includes at least a first metric related to data froma first application and a second metric related to data from the firstapplication; a second complication that includes at least a third metricrelated to data from a second application and a fourth metric related todata from the second application; and a third complication that includesat least a fifth metric related to data from a third application and asixth metric related to data from the third application; a means fordetecting a sequence of one or more inputs that corresponds to a requestto add a fourth complication to the watch user interface, wherein thefourth complication includes at least a seventh metric related to datafrom a fourth application and an eighth metric related to data from thefourth application; and in response to detecting the sequence of one ormore inputs: in accordance with a determination that the sequence of oneor more inputs corresponds to a request to replace the firstcomplication, a means for replacing the first complication with thefourth complication; in accordance with a determination that thesequence of one or more inputs corresponds to a request to replace thesecond complication, a means for replacing the second complication withthe fourth complication; and in accordance with a determination that thesequence of one or more inputs corresponds to a request to replace thethird complication, a means for replacing the third complication withthe fourth complication.

In some embodiments, a method is described. The method comprises: at anelectronic device with a display and one or more input devices,displaying, on the display, a watch user interface, the watch userinterface including: a clock face; and a user interface element at leastpartially surrounding the clock face. The method further comprisesreceiving, via the one or more input devices, a request to add arespective complication to a respective location on the clock face and,in response to receiving the request to add the respective complicationto the respective location on the clock face: in accordance with adetermination that the respective complication is a first complication,displaying, on the display, the first complication in the respectivelocation on the clock face and replacing at least a portion of the userinterface element with content associated with the first complication;and in accordance with a determination that the respective complicationis a second complication, displaying, on the display, the secondcomplication in the respective location on the clock face withoutreplacing the portion of the user interface element with contentassociated with the second complication.

In some embodiments, a non-transitory computer readable storage mediumis described. The non-transitory computer readable storage medium storesone or more programs configured to be executed by one or more processorsof an electronic device with a display and one or more input devices.The one or more programs include instructions for: displaying, on thedisplay, a watch user interface, the watch user interface including: aclock face; and a user interface element at least partially surroundingthe clock face. The one or more programs further include instructionsfor receiving, via the one or more input devices, a request to add arespective complication to a respective location on the clock face and,in response to receiving the request to add the respective complicationto the respective location on the clock face: in accordance with adetermination that the respective complication is a first complication,displaying, on the display, the first complication in the respectivelocation on the clock face and replacing at least a portion of the userinterface element with content associated with the first complication;and in accordance with a determination that the respective complicationis a second complication, displaying, on the display, the secondcomplication in the respective location on the clock face withoutreplacing the portion of the user interface element with contentassociated with the second complication.

In some embodiments, a transitory computer readable storage medium isdescribed. The transitory computer readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display and one or more input devices. The oneor more programs include instructions for: displaying, on the display, awatch user interface, the watch user interface including: a clock face;and a user interface element at least partially surrounding the clockface. The one or more programs further include instructions forreceiving, via the one or more input devices, a request to add arespective complication to a respective location on the clock face and,in response to receiving the request to add the respective complicationto the respective location on the clock face: in accordance with adetermination that the respective complication is a first complication,displaying, on the display, the first complication in the respectivelocation on the clock face and replacing at least a portion of the userinterface element with content associated with the first complication;and in accordance with a determination that the respective complicationis a second complication, displaying, on the display, the secondcomplication in the respective location on the clock face withoutreplacing the portion of the user interface element with contentassociated with the second complication.

In some embodiments, an electronic device is described. The electronicdevice comprises: a display, one or more input devices; one or moreprocessors; and memory storing one or more programs configured to beexecuted by the one or more processors. The one or more programs includeinstructions: displaying, on the display, a watch user interface, thewatch user interface including: a clock face; and a user interfaceelement at least partially surrounding the clock face. The one or moreprograms further include instructions for receiving, via the one or moreinput devices, a request to add a respective complication to arespective location on the clock face and, in response to receiving therequest to add the respective complication to the respective location onthe clock face: in accordance with a determination that the respectivecomplication is a first complication, displaying, on the display, thefirst complication in the respective location on the clock face andreplacing at least a portion of the user interface element with contentassociated with the first complication; and in accordance with adetermination that the respective complication is a second complication,displaying, on the display, the second complication in the respectivelocation on the clock face without replacing the portion of the userinterface element with content associated with the second complication.

In some embodiments, an electronic device is described. The electronicdevice comprises: a means for displaying, on the display, a watch userinterface, the watch user interface including: a clock face; and a userinterface element at least partially surrounding the clock face. Theelectronic device further comprises, a means for receiving, via the oneor more input devices, a request to add a respective complication to arespective location on the clock face and in response to receiving therequest to add the respective complication to the respective location onthe clock face. The device further comprises: a means for displaying, onthe display, the first complication in the respective location on theclock face and replacing at least a portion of the user interfaceelement with content associated with the first complication inaccordance with a determination that the respective complication is afirst complication; and a means for displaying, on the display, thesecond complication in the respective location on the clock face withoutreplacing the portion of the user interface element with contentassociated with the second complication in accordance with adetermination that the respective complication is a second complication.

In some embodiments, a method is described. The method comprises, at anelectronic device with a display and one or more input devices,displaying, on the display, a watch user interface, the watch userinterface including: a clock face; a user interface element at leastpartially surrounding the clock face; and a complication. The methodfurther comprises: while displaying the watch user interface, detecting,via the one or more input devices, an input directed to the userinterface element; and in response to detecting the input directed tothe user interface element, updating, on the display, an appearance ofthe user interface element based on the input while maintaining displayof the clock face and the complication on the display.

In some embodiments, a non-transitory computer readable storage mediumis described. The non-transitory computer readable storage medium storesone or more programs configured to be executed by one or more processorsof an electronic device with a display and one or more input devices.The one or more programs include instructions for: displaying, on thedisplay, a watch user interface, the watch user interface including: aclock face; a user interface element at least partially surrounding theclock face; and a complication. The one or more programs further includeinstructions for: while displaying the watch user interface, detecting,via the one or more input devices, an input directed to the userinterface element; and in response to detecting the input directed tothe user interface element, updating, on the display, an appearance ofthe user interface element based on the input while maintaining displayof the clock face and the complication on the display.

In some embodiments, a transitory computer readable storage medium isdescribed. The transitory computer readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display and one or more input devices. The oneor more programs include instructions for: displaying, on the display, awatch user interface, the watch user interface including: a clock face;a user interface element at least partially surrounding the clock face;and a complication. The one or more programs further includeinstructions for: while displaying the watch user interface, detecting,via the one or more input devices, an input directed to the userinterface element; and in response to detecting the input directed tothe user interface element, updating, on the display, an appearance ofthe user interface element based on the input while maintaining displayof the clock face and the complication on the display.

In some embodiments, an electronic device is described. The electronicdevice comprises: a display, one or more input devices; one or moreprocessors; and memory storing one or more programs configured to beexecuted by the one or more processors. The one or more programs includeinstructions for: displaying, on the display, a watch user interface,the watch user interface including: a clock face; a user interfaceelement at least partially surrounding the clock face; and acomplication. The one or more programs further include instructions for:while displaying the watch user interface, detecting, via the one ormore input devices, an input directed to the user interface element; andin response to detecting the input directed to the user interfaceelement, updating, on the display, an appearance of the user interfaceelement based on the input while maintaining display of the clock faceand the complication on the display.

In some embodiments, an electronic device is described. The electronicdevice comprises: a means for displaying, on the display, a watch userinterface, the watch user interface including: a clock face; a userinterface element at least partially surrounding the clock face; and acomplication. The device further comprises a means for detecting, viathe one or more input devices, while displaying the watch userinterface, an input directed to the user interface element. The devicefurther comprises a means for updating, on the display, an appearance ofthe user interface element based on the input while maintaining displayof the clock face and the complication on the display, in response todetecting the input directed to the user interface element.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for providing context-specific user interfaces, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces can complement or replaceother methods for providing context-specific user interfaces.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6M illustrate exemplary context-specific user interfaces.

FIGS. 7A-7B illustrate a flow diagram depicting a method for providingcontext-specific user interfaces in accordance with some embodiments.

FIGS. 8A-8J illustrate exemplary context-specific user interfaces.

FIG. 9 illustrates a flow diagram depicting a method for providingcontext-specific user interfaces in accordance with some embodiments.

FIGS. 10A-10T illustrate exemplary context-specific user interfaces.

FIGS. 11A-11D illustrate a flow diagram depicting a method for providingcontext-specific user interfaces in accordance with some embodiments.

FIGS. 12A-12R illustrate exemplary context-specific user interfaces.

FIG. 13 illustrates a flow diagram depicting a method for providingcontext-specific user interfaces in accordance with some embodiments.

FIGS. 14A-14AE illustrate exemplary context-specific user interfaces.

FIGS. 15A-15C illustrate a flow diagram depicting a method for providingcontext-specific user interfaces in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for providing context-specific user interfaces, e.g.,that display the time along with additional information. This isparticularly true for portable multifunction devices with reduced-sizedisplays. Providing the user with relevant information (e.g., obtainedfrom one or more applications) at a glance in a convenient, customizableinterface reduces the number of inputs needed to access the informationand conserves battery life. Moreover, providing user with an interfacethat can be rapidly adapted to display a variety of content at differentlevels of detail as the context in which the user is using theinterfaces changes (e.g., throughout the day) makes accessing suchinformation through the interfaces even more efficient. Such aninterface provides more efficient use of screen “real estate,” which inturn reduces the number of user interactions required to access relevantdata at any time of day. Such techniques can reduce the cognitive burdenon a user who uses the context-specific user interfaces to accessinformation and/or keep time, thereby enhancing productivity. Further,such techniques can reduce processor and battery power otherwise wastedon redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for configuringcontext-specific user interfaces. FIGS. 6A-6M, 8A-8J, 10A-10T, 12A-12R,and 14A-14AE illustrate exemplary user interfaces for providingcontext-specific user interfaces. The user interfaces in these figuresare also used to illustrate the processes described below, including themethods in FIGS. 7A-7B, 9, 11A-11D, 13, and 15A-15C.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2) optionally include an up/down buttonfor volume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including methods 700, 900,and 1100 (FIGS. 7A-7B, 9, 11A-11D, 13, and 15A-15C). A computer-readablestorage medium can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. In some examples,the storage medium is a transitory computer-readable storage medium. Insome examples, the storage medium is a non-transitory computer-readablestorage medium. The non-transitory computer-readable storage medium caninclude, but is not limited to, magnetic, optical, and/or semiconductorstorages. Examples of such storage include magnetic disks, optical discsbased on CD, DVD, or Blu-ray technologies, as well as persistentsolid-state memory such as flash, solid-state drives, and the like.Personal electronic device 500 is not limited to the components andconfiguration of FIG. 5B, but can include other or additional componentsin multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, device 500, ordevice 600.

FIGS. 6A-6M illustrate exemplary context-specific user interfaces thatcan be used for controlling the display of graphical elements with userinput, in accordance with some embodiments. The user interfaces in thesefigures are used to illustrate the processes described below, includingthe methods in FIG. 7A-7B.

FIG. 6A illustrates device 600 with display 602 and rotatable inputmechanism 604 (e.g., rotatable in relation to a housing or frame of thedevice). In some embodiments, device 600 is a wearable electronicdevice, such as smartwatch. In some embodiments, device 600 includes oneor more features of devices 100, 300, or 500. As illustrated in FIG. 6A,device 600 displays watch user interface 601 on display 602. Watch userinterface 601 includes graphical objects 606, 608-1, 608-2, and 608-3.In FIG. 6A, graphical object 606 includes an indication of time. Asillustrated in FIG. 6A, the indication of time includes a representationof an analog clock face with hour hand 616-1, minute hand 616-2, andsecond hand 616-3. As used here, second hand 616-3 refers to arepresentation of a clock hand that indicates a seconds component oftime, as opposed to a second hand of two or more hands (e.g., a firsthand, second hand, third hand, etc.). In some embodiments, theindication of time is a representation of digital clock including anumerical indication of an hour and a numerical indication of a minute.

In FIG. 6A, graphical objects 608-1, 608-2, and 608-3 are complications(collectively “complications 608”) corresponding to respectiveapplications. In some embodiments, one or more of complications 608display data from their respective applications. In some embodiments,one or more of graphical objects 608-1, 608-2, or 608-3 is not acomplication.

A complication refers to any clock face feature other than those used toindicate the hours and minutes of a time (e.g., clock hands orhour/minute indications). In some embodiments, complications providedata obtained from an application. In some embodiments, a complicationincludes an affordance that when selected launches a correspondingapplication. In some embodiments, a complication is displayed at afixed, predefined location on the display.

In FIG. 6A, complications 608-1, 608-2, and 608-3 occupy respectivelocations at the lower-right, lower-left, and upper-left on watch userinterface 601, while clock face 606 occupies a location in theupper-right on watch user interface 601. In FIG. 6A, each location isoffset from the center of watch user interface 601. The lower-right,lower-left, and upper-left locations make up a sequence of locations ondisplay 602, in which lower-right is the first location in the sequenceof locations, lower-left is the second location in the sequence oflocations, and upper-left is the third (and last) location in thesequence of locations. As shown in FIG. 6A, the locations are associatedwith respective sizes that determine the size of a graphical objectdisplayed at a particular location. Of the three locations in thesequence of locations, the third (last) location (upper-left) has thesmallest size; the second location (lower-left) has the largest size;and the first location (lower-right) has a size between the size of thesecond location and the size of the third location.

In some embodiments, the locations on watch user interface 601 are in adifferent order in the sequence than described above (e.g., upper-left,lower-right, lower left; upper-left, lower-left, lower-right;lower-left, lower-right, upper-left; etc.). In some embodiments, thesequence of locations includes only two locations (e.g., lower-left andlower-right). In some embodiments, the sequence of locations includesmore than three locations. In some embodiments, locations that areadjacent in the sequence of locations are not adjacent on display 602.In some embodiments, the areas associated with the locations are a shapeother than circular (e.g., rectangular).

In FIG. 6A, device 600 received (e.g., detects) user input 690-1, whichincludes rotation of rotatable input mechanism 604 in an upward(clockwise) direction (e.g., as seen by comparing the positions of thefinger shown in FIGS. 6A and 6B).

As illustrated in FIG. 6B, in response to receiving (e.g., detecting)user input 690-1, device 600 changes the locations at whichcomplications 608-1, 608-2, and 608-3 are displayed (e.g., based on thesequence of locations). Each complication moves to the next location inthe sequence, with exception of complication 608-3, which moves from thethird (last) location to the first location. Complication 608-1 ceasesto be displayed at the first location (lower-right) and is displayed atthe second location (lower-left); complication 608-2 ceases to bedisplayed at the second location (lower-left) and is displayed at thethird (last) location (upper-left); and complication 608-3 ceases to bedisplayed at the third (last) location (upper-left) and is displayed atthe first location (lower-right).

Complications 608-1, 608-2, or 608-3 are modified when moving from onelocation to another. Due to the different sizes associated with thelocations, complication 608-1 increases in size, complication 608-2decreases in size, and complication 608-3 increases in size.

In some embodiments, the information included in one or more of thecomplications changes when moving from one location to another. In FIG.6A, complication 608-1 includes a current temperature 610 and a partialring with indicator 612 that shows the current temperature relative tothe (e.g., forecasted) temperature range 614 of a high temperature (86degrees) and low temperature (52 degrees). When displayed at the second(lower-left) location as shown in FIG. 6B, complication 608-1additionally includes weather condition indicator 618 (e.g., indicatingthat a current weather condition is sunny). As another example,complication 608-3 includes a heart icon at the third location(upper-left) and includes indication 620 of heart beats per minute (70BPM) in the larger first location (lower-right).

In some embodiments, the information included in a complication does notchange when moving from one location to another (e.g., the informationincluded in a complication does not depend on location). For example,complication 608-2 is an astronomy complication that includes arepresentation of Earth as currently illuminated by the Sun (e.g.,showing day and night regions). In some embodiments, astronomycomplication 608-2 includes an indication (e.g., a dot) showing thelocation of device 600 on Earth. As illustrated in FIGS. 6A and 6B,complication 608-2 appears the same (except for size) at both the second(lower-left) location and the third (last; upper-left).

As illustrated in FIG. 6B, device 600 receives (e.g., detects) userinput 690-2, which includes rotation of rotatable input mechanism 604further in the same direction as the rotation of user input 690-1. Insome embodiments, user input 690-2 is a continuation of user input690-1. In some embodiments, user input 690-2 is separate from user input690-1.

As illustrated in FIG. 6C, in response to receiving user input 690-2,device 600 further changes the locations of complications 608-1, 608-2,and 608-3 (e.g., based on the sequence of locations). Complication 608-1ceases to be displayed at the second location (lower-left) and isdisplayed at the third location (upper-left); complication 608-2 ceasesto be displayed at the third location (upper-left) and is displayed atthe first location (lower-right); and complication 608-3 ceases to bedisplayed at the first location (lower-right) and is displayed at thesecond location (lower-left). Complication 608-1 decreases in size andincludes less information. At the third location, complication 608-1 isdisplayed with current temperature 610 and temperature range ring withindicator 612, but without temperature range 614 showing the high andlow temperatures and weather condition indicator 618 (e.g., without atleast some information displayed at the second location). Complication608-2 increases in size and continues to include a representation ofEarth as currently illuminated by the Sun. Complication 608-3 increasesin size and includes further information, low heart rate 622 and highheart rate 624, in addition to current heart rate 620, which wasprovided at the first location. The addition of information ascomplication 608-3 moves to progressively larger locations (e.g., thirdto first to second) illustrates an embodiment of a manner in which acomplication can provide progressively more information as it moves tolocations of progressively increasing size. Similarly, complication608-1 includes more information as it moves from the first location tothe larger second location, but includes less information when it movesfrom the second location (e.g., the largest location) to the thirdlocation (e.g., the smallest location).

As illustrated in FIG. 6C, device 600 receives (e.g., detects) userinput 690-3, which includes rotation of rotatable input mechanism 604further in the same direction as the rotation of user input 690-1 anduser input 690-2. In some embodiments, user input 690-3 is acontinuation of user input 690-2. In some embodiments, user input 690-2is separate from user input 690-2.

As illustrated in FIG. 6D, in response to receiving user input 690-3,device 600 further changes the locations of complications 608-1, 608-2,and 608-3 (e.g., based on the sequence of locations). Complication 608-1ceases to be displayed at the third (last) location (upper-left) and isdisplayed at the first location (lower-right); complication 608-2 ceasesto be displayed at the first location (lower-right) and is displayed atthe second location (lower-left); and complication 608-3 ceases to bedisplayed at the second location (lower-left) and is displayed at thethird (last) location (upper-left). In response to user inputs 690-1thru 690-3, complications 608 cycle sequentially through the sequence oflocations and return to the locations initially occupied in FIG. 6A.

As illustrated in FIGS. 6A-6D, complications 608 progress forward in thesequence of locations until reaching the last location, at which pointcomplications 608 move to the first location in the sequence. Due to therelative positions of the locations on display 602, this results incomplications 608 moving in a clockwise direction. In some embodiments,the direction (in either the logical sequence of locations or physicaldirection on display 602) depends on the user input (e.g., the directionof the user input). For example, complications 608 cycle in thedirection illustrated in FIGS. 6A-6D in accordance with the direction ofuser inputs 690-1 thru 690-3 (e.g., upward or clockwise rotation ofrotatable input mechanism 604).

FIGS. 6E-6H illustrate movement of complications 608 in response to userinputs 692-1 thru 692-3 having a direction opposite the direction ofuser inputs 690-1 thru 690-3 (e.g., downward or counter-clockwiserotation of rotatable input mechanism 604). As shown in FIGS. 6E-6H, inresponse to user inputs 692-1 thru 692-3, complications 608 movebackward in the sequence of locations (e.g., counter-clockwise ondisplay 602). For example, complication 608-1 moves from the firstlocation, to the last location, to the second location, and back to thefirst location. In some embodiments, complications 608 move forward inthe sequence of locations in response to a swipe gesture on display 602having a first direction (e.g., up or right) and move backward in thesequence of location in response to a swipe gesture having an oppositedirection (e.g., down or left).

As illustrated in FIGS. 6A-6H, clock face 606 remains in the upper-rightlocation of watch user interface 601 during user inputs 690 and 692,even as complications 608 are moved (e.g., the upper-right location isnot included in the sequence of locations between which graphicalobjects move in response to user input). In some embodiments, theupper-right location on watch user interface 601 is included in thesequence of locations (e.g., as a fourth (last) location), and clockface 606 is moved to different locations in the sequence along withcomplications 608.

FIGS. 6I-6M illustrate an embodiment with a sequence of locations inwhich the lower-right location is the first location, the lower-leftlocation is the second location, the upper-left location is the thirdlocation, and the upper-right location is the fourth (last) location. Asillustrated in FIGS. 6I-6M, graphical objects 606, 608-1, 608-2, and608-3 move forward in the sequence of locations (e.g., clockwise ondisplay 602) in response to user inputs 693-1 thru 693-4.

As illustrated in FIGS. 6I-6M, the fourth location has a size largerthan the size of the second location (e.g., previously the location withthe largest size), which allows for display of additional informationcompared to the first, second, and third locations. When complication608-3 is positioned at the fourth location (FIG. 6K), it includesadditional information 628 indicating when the currently displayed hearrate 620 was last updated, as compared to the information included whencomplication 608-3 is positioned at the location with the next largestsize (the second location) (FIG. 6M). Complication 608-1 also includesadditional location information 630 in the fourth location (FIG. 6M) ascompared to the second location (FIG. 6K). Clock face 606 includesprogressively more detail as the size of the location increases beyond acertain size. At the three smallest locations (the first, second, andthird locations) clock face 606 includes the same amount of detail(e.g., tick marks 636 corresponding to hour markers), while at thelargest location (the fourth location) clock face 606 includes numerals626 corresponding to the hour markers.

As illustrated in FIGS. 6A-6H, the locations are fixed in the sense thatthe positions of the locations do not change or move as differentgraphical objects are displayed at the locations in response to userinput (e.g., a graphical object displayed at a particular locationalways occupies the same area of display 602).

In some embodiments, ceasing to display a complication at one locationand displaying the complication at another location includes ananimation while ceasing to display the complication, an animation whiledisplaying the complication, or an animation while ceasing to displaythe complication and while displaying the complication (e.g., thecomplication gradually fades away or gradually appears or thecomplication translates off of one location and translates into anotherlocation).

As illustrated in FIG. 6J, in some embodiments, watch user interface 601displays an animation of complications 608-1, 608-2, and 608-3 and clockface 606 moving in a clockwise direction as each element translates offof one location and translates into the next location in the sequence oflocations on the display. For example, as complications 608 transitionfrom the configuration illustrated in FIG. 6I to the configurationillustrated in FIG. 6K, the watch user interface 601, displayscomplications 608-1, 608-2, and 608-3 and clock face 606 in intermediatepositions (e.g., complication 608-1 is between the first position andthe second position, complication 608-2 is between the second positionand the third position, complication 608-3 is between the third positionand the fourth (last) position, and clock face 606 is between fourth(last) position and the first position). In some embodiments, thedirection of the animated movement of each graphical element correspondsto the direction of user input 693-2 (e.g., complications 608 translatein clockwise direction in response to a clockwise input 693-2 at therotatable input mechanism).

FIGS. 7A-7B are a flow diagram illustrating a method for providingcontext-specific user interfaces using an electronic device inaccordance with some embodiments. Method 700 is performed at a device(e.g., 100, 300, 500, 600) with a display. Some operations in method 700are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

At block 702, the device displays a watch user interface (e.g., 601) onthe display (e.g., 602). The watch user interface includes a firstgraphical object at a first location (e.g., 608-1 of FIG. 6A) in asequence of locations on the display and a second graphical object at alast location (e.g., 608-3 of FIG. 6A) in the sequence of locations onthe display. In some embodiments, at least one of the first graphicalobject and the second graphical object display data from an application(e.g., the first graphical object and/or the second graphical object isa complication associated with a watch face of the watch userinterface). In some embodiments, the first graphical object includes anindication of time (606). In some embodiments, the indication of time isa representation of an analog clock including an hour hand and a minutehand. In some embodiments, the indication of time is a representation ofdigital clock including a numerical indication of an hour and anumerical indication of a minute. In some embodiments, the indication oftime is offset from the center of the display.

Displaying multiple graphical elements as members of sequence oflocations on a display, which can be re-configured in a sequentialmanner, provides the user with feedback about the current position of anindividual graphical element relative to other graphical elements andprovides visual feedback to the user indicating how subsequent inputswill alter the display. Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

At block 704, the device detects a user input. In some embodiments, thedevice has a rotatable input mechanism (e.g., 604), and the user inputincludes rotation of the rotatable input mechanism (e.g., 690). In someembodiments, the rotatable input mechanism is a physical mechanismattached to a fixed location of the electronic device (e.g., the side ofthe frame 603) and rotates relative to the electronic device. In someembodiments, the movement of complications between locations on thedisplay is based on the direction of rotation (e.g., rotation in onedirection results in forward movement in the sequence of locations, androtation in the opposite direction results in backward movement in thesequence of locations).

In some embodiments, the user input is a swipe gesture detected on thedisplay (e.g., in a first direction).

In response to detecting the user input, the device performs theoperations of blocks 706, 708, 710, and 712. At block 706, the deviceceases to display the first graphical object at the first location inthe sequence of defined locations on the display (e.g., 608-1 of FIG. 6Ain the lower-right of the display). At block 708, the device ceases todisplay the second graphical object at the last location in the sequenceof defined locations on the display (e.g., 608-3 of FIG. 6A in theupper-left of the display). At block 710, the device displays the secondgraphical object at the first location in the sequence of locations onthe display (e.g., 608-3 of FIG. 6B is displayed in the lower-right ofthe display). At block 712, the device displays the first graphicalobject at a second location in the sequence of locations on the display(e.g., 608-1 of FIG. 6B is displayed in the lower-left of the display).In some embodiments, there are only 2 locations and the second locationis the last location. In some embodiments, there are more than 2locations and the second location is the next location in the sequence(e.g., FIGS. 6A-6M). In some embodiments, the first graphical object,while displayed at the first location, includes first information andthe first graphical object, while displayed at the second location,includes second information, different than the first information (e.g.,without including the first information) (e.g., 608-1 of FIG. 6A and608-1 of FIG. 6B).

Automatically updating a visual characteristic, such as the type andquantity of information displayed on multiple graphical elements inresponse to a change in location on the interface caused by an input,provides the user with more control over the device by helping the userquickly configure multiple display elements into a varietyconfigurations without the requiring individual interactions with eachelement (e.g., first selecting an element, then relocating the elementto another location on the display, individually adjusting nature ofinformation displayed and repeating the steps for other elements arecondensed into fewer operations that require user input). Reducing thenumber of inputs need to perform equivalent operations, enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the first graphical object has a first size whiledisplayed at the first location, and wherein the first graphical objecthas a second size while displayed at the second location, the first sizedifferent than the second size. (e.g., 608-1 of FIG. 6B and 608-1 ofFIG. 6C).

Automatically updating a visual characteristic, such as size, ofmultiple graphical elements in response to a change in location on aninterface caused by an input, provides the user with more control overthe device by helping the user quickly configure multiple displayelements into a variety configurations without the requiring individualinteractions with each element (e.g., first selecting an element, thenrelocating the element to another location on the display, then resizingof the element and repeating these steps for other elements arecondensed in fewer operations that require user input). Reducing thenumber of inputs need to perform equivalent operations, enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the watch user interface further includes anindication of time that is displayed at the same position before andafter the first input (e.g., 606 of FIGS. 6A-6H). In some embodiments,the indication of time is a representation of an analog clock includingan hour hand and a minute hand (e.g., 606). In some embodiments, theindication of time is a representation of digital clock including anumerical indication of an hour and a numerical indication of a minute.

Ceasing to display the first and the second graphical elements at thefirst and last locations, respectively, then redisplaying the secondgraphical element at the first location and the first graphical elementat second location in response to an input provides the user with morecontrol over the device by helping the user quickly configure multipledisplay elements into a variety configurations without requiringindividual interactions with each element. Reducing the number of inputsneed to perform equivalent operations, enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, ceasing to display the first graphical object atthe first location in the sequence of defined locations on the displayand displaying the first graphical object at the second location in thesequence of locations on the display includes displaying an animation ofthe first graphical object moving from the first location toward thesecond location and ceasing to display the second graphical object atthe last location in the sequence of defined locations on the displayand displaying the second graphical object at the first location in thesequence of locations on the display includes displaying an animation ofthe second graphical object moving from the last location toward thefirst location (e.g., in response to the input (e.g., 693), the device(e.g., 600) displays an animation illustrated by FIGS. 6I to 6K).

Displaying animations of objects as they are reassigned to differentlocations on a user interface, provides the user with visual feedbackabout how subsequent interactions with the device will specificallychange the configuration of the user interface, this feedback enablesthe user to choose their next input more efficiently. Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first location and the second location arefixed on the display relative to a physical frame of the device (e.g.,the positions of the first location and the second location do notchange in response to detecting the first input). In some embodiments,in response to the first input, the second graphical object ceases to bedisplayed at the last location and is displayed at the first locationwithout animating movement of the second graphical object from the lastlocation to the first location.

In some embodiments, at block 714 the device detects a second user inputhaving a second direction opposite the direction of the first input(e.g., 692). In response to detecting the second user input (e.g.,692-3), the device performs the operations of blocks 716, 718. 720, and722 (e.g., 608-1, FIG. 6G to 6H). At block 716, the device ceases todisplay the first graphical object at the second location in thesequence of defined locations on the display (e.g., 608-1). At block718, the device ceases to display the second graphical object (e.g.,608-2) at the first location in the sequence of defined locations on thedisplay. At block 720, the device displays the second graphical objectat the last location in the sequence of locations on the display (e.g.,608-2 of FIG. 6H). At block 722, the device displays the first graphicalobject at a first location in the sequence of locations on the display(e.g., 608-1 of FIG. 6H).

Updating the positioning of multiple graphical elements on a displayconsistent with the direction of a user input provides the user withfeedback about how subsequent interactions with the device will changethe configuration of user interface, this enables the user to choosetheir next input more efficiently. Providing improved visual feedback tothe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

As described below, method 700 provides an intuitive way for configuringcontext-specific user interfaces. The method reduces the cognitiveburden on a user, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user toconfigure context-specific user interfaces faster and more efficientlyconserves power and increases the time between battery charges.

Note that details of the processes described above with respect tomethod 700 (e.g., FIGS. 7A-7B) are also applicable in an analogousmanner to the methods described below (e.g., methods 900 and 1100). Forexample, method 1100 optionally includes one or more of thecharacteristics of the various methods described above with reference tomethod 700. For example, the positions of complications 1008 of FIG. 10Aon watch user interface 1000 can be reconfigured (e.g., cycled in aclockwise direction) in response to a user input at the rotatable inputdevice 604 in a manner analogous to various technique described withreference to method 700. For brevity, these details are not repeatedbelow.

FIGS. 8A-8J illustrate exemplary user interfaces for displaying abackground of a watch user interface, in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the methods in FIG. 9.

FIG. 8A illustrates device 600 as described above. In FIG. 8A, device600 displays watch user interface 801 on display 602 at a first time(10:15:35). As illustrated in FIG. 8A watch user interface 801 includesan hour hand 806-1, minute hand 806-2, and second hand 806-3. As usedhere, second hand 806-3 refers to a representation of a clock hand thatindicates a seconds component of time, as opposed to a second hand oftwo or more hands (e.g., a first hand, second hand, third hand, etc.).In some embodiments, watch user interface includes only hour hand 806-1and minute hand 806-2 (e.g., not second hand 806-3) or only hour hand806-1 (e.g., not minute hand 806-2 and second hand 806-3).

Hour hand 806-1, minute hand 806-2, and second hand 806-3 are overlaidon background 810, which includes first portion 810-1 and second portion810-2 separated by straight linear boundary 812. In some embodiments,background 810 includes a boundary that is not linear. As indicated bythe stippling on first portion 810-1 in FIG. 8A, first portion 810-1 hasa different color or visual pattern than second portion 810-2. In FIG.8A, background 810 occupies the entire background of display 602 (e.g.,background 810 extends to the edges and (rounded) corners of display602).

Background 810 includes one or more graphical characteristics based onthe position of hour hand 806-1. As illustrated in FIG. 8A, linearboundary 812 is aligned along hour hand 806-1, which defines theorientation of background 810 with respect to a physical feature ofdevice 600 (e.g., display 602, frame 603, rotatable input mechanism 604,and button 605). As oriented in FIG. 8A, first portion 810-1 ispositioned generally above and to the right of second portion 810-2, andgenerally occupies the upper right half of display 602. Hour hand 806-1extends from a point in the center of display 602. As a result, linearboundary 812 extends from one edge of display 602 (e.g., left edge asshown in FIG. 8A) to an opposite edge (e.g., right edge) such that firstportion 810-1 and second portion 810-2 each occupy half of the area ofdisplay 602.

Turning now to FIG. 8B, device 600 displays watch user interface 801 ata second time (12:00:58) (e.g., after the first time), with a secondgraphical characteristic (e.g., re-orientated position) of background810 based on the updated position of hour hand 806-1. As illustrated inFIG. 8B, linear boundary 812 remains aligned along hour hand 806-1 andis vertically oriented such that first portion 810-1 occupies the righthalf of display 602 and second portion 810-2 occupies the left half ofdisplay 602.

FIGS. 8C and 8D illustrate that linear boundary 812 remains alignedalong hour hand 806-1 as the time and hour hand 806-1 progresses to 3:00(FIG. 8C) and 4:30 (FIG. 8D), with background 810 rotating with hourhand 806-1. As illustrated in FIGS. 8A-8D, background 810 rotates aroundthe same point (e.g., a common origin) as hour hand 806-1.

As illustrated in FIGS. 8A-8D, watch user interface 801 also includesgraphical elements (e.g., hour numerals (1-12) and date object (808)(e.g., a calendar complication)), which are overlaid on the backgroundand remain fixed (e.g., in the same place with respect to display 602)as hour hand 806-1, minute hand 806-2, second hand 806-3, and background810 change position on display 602.

As illustrated in FIGS. 8A-8D, the shapes of first portion 810-1 andsecond portion 810-2 change as background 810 rotates. For example, inFIGS. 8B and 8C, portions 810-1 and 810-2 are roughly rectangular (withthe exception of the rounded corners due to the shape of display 602),while in FIG. 8D, portions 810-1 and 810-2 are roughly triangular (withthe exception of the rounded corners due to the shape of display 602).

As illustrated in FIGS. 8A-8D, background 810 remains fixed relative tohour hand 806-1 (e.g., first portion 810-1 remains on the clockwise sideof hour hand 806-1). In some embodiments, first portion 810-1 is on thecounter-clockwise side hour hand 806-1. In the embodiment illustrated inFIGS. 8A-8D, the graphical characteristic of background 810 repeatsevery twelve hours (e.g., background 810 makes a complete rotation everytwelve hours). At each time (e.g., 6:00), first portion 810-1 occupiesan area of display 602 that is occupied by second portion 810-2 at adifferent time (e.g., 12:00), and vice versa (e.g., first portion 810-1and second portion 810-2 switch positions every six hours).

Turning now to FIGS. 8E-8H, an embodiment in which a graphicalcharacteristic of background 810 is based on the position of minute hand806-2 is illustrated. As illustrated in FIGS. 8E-8H, linear boundary 812remains aligned along minute hand 806-2 as minute hand 806-2 rotates ondisplay 602. Background 810 rotates with minute hand 806-2 around apoint in the center of display 602 similar to the way in whichbackground 810 rotates with hour hand 806-1 as illustrated in FIGS.8A-8D. First portion 810-1 and second portion 810-2 each occupyrespective halves of display 602 and change shape as the position ofminute hand 806-2 changes over time. In the embodiment illustrated inFIGS. 8E-8H, the graphical characteristic of background 810 repeatsevery hour (e.g., background 810 makes a complete rotation every hour).First portion 810-1 and second portion 810-2 switch positions everythirty minutes. In contrast to FIGS. 8A-8D, first portion 810-1 remainson the counter-clockwise side of minute hand 806-2. In some embodiments,first portion 810-1 is on the clockwise side of minute hand 806-2. Insome embodiments, a graphical characteristic is based on the position ofsecond hand 806-3 in a manner analogous to the manner described abovefor hour hand 806-1 and minute hand 806-2.

Turning now to FIGS. 8I and 8J, an embodiment with a differentbackground is described. As illustrated in FIGS. 8I and 8J, watch userinterface 801 includes background 818, which includes a spotlight effect814. A graphical characteristic of background 818 (e.g., the position ofspotlight effect 814) is based on the position of hour hand 806-1. Asillustrated in FIGS. 8I and 8J, spotlight effect 814 is displayed behindthe hour marker 816 corresponding to the position of hour hand 806-1. Insome embodiments, spotlight 814 remains constantly aligned along hourhand 806-1 (e.g., spotlight effect 814 is displayed between hour markers11 and 12 at 11:30). In some embodiments, spotlight 814 remains behindan hour marker corresponding to the current hour (e.g., spotlight effect814 remains behind hour marker 11 from 11:00 to 11:59).

In some embodiments, the hand upon which the graphical characteristic ofbackground 810 is based is determined (e.g., selected) based on userinput. In some embodiments, in response to receiving a sequence of oneor more user inputs, device 602 operates in a mode in which a graphicalcharacteristic of background 810 is based on hour hand 806-1, minutehand 806-2, or second hand 806-3 (e.g., in response, at least in part,to selection of one or more affordances for accessing and selecting amenu option corresponding to one of hands 806). In some embodiments,selecting the hand upon which the graphical characteristic of background810 is based includes entering a watch face edit mode or a watch facesettings edit mode (e.g., in response to determining that a receivedcontact has a characteristic intensity greater than or equal to athreshold intensity).

In some embodiments, in response to receiving a sequence of one or moreuser inputs, device 602 switches from a mode in which a graphicalcharacteristic of background 810 is based on one hand (e.g., hour hand806-1) to a mode in which a graphical characteristic of background 810is based on a different hand (e.g., minute hand 806-2). In this way, auser can select the rate at which the graphical characteristic (e.g.,orientation) of the background changes (e.g., rotates).

In some embodiments, the background and/or graphical characteristic ofthe background is determined (e.g., selected) based on user input. Insome embodiments, in response to receiving a sequence of one or moreuser inputs, device 602 set the background and/or graphicalcharacteristic to a selected background and/or graphical characteristic(e.g., in response to selection of one or more affordances for accessingand selecting a menu option corresponding to the background and/orgraphical characteristic). In some embodiments, in response to receivinga sequence of one or more user inputs, device 602 switches from onebackground and/or graphical characteristic (e.g., background 810) to adifferent background and/or graphical characteristic (e.g., background818).

FIG. 9 is a flow diagram illustrating a method for providingcontext-specific user interfaces using an electronic device inaccordance with some embodiments. Method 900 is performed at a device(e.g., 100, 300, 500, 600) with a display. Some operations in method 900are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 900 provides an intuitive way for configuringcontext-specific user interfaces. The method reduces the cognitiveburden on a user, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user toconfigure context-specific user interfaces faster and more efficientlyconserves power and increases the time between battery charges.

At block 902, the device displays watch user interface (e.g., 801) onthe display (e.g., 602) at a first time. The watch user interface at thefirst time includes a first clock hand in a first position (e.g., FIG.8A, 806-1) overlaid on a background (e.g., 810), the background having afirst graphical characteristic at the first time that is determinedbased on the first position of the first clock hand (e.g., theappearance of 810 is based on the position 806-1).

In some embodiments, the first clock hand is one of an hour hand, aminute hand, or a second hand (e.g., 806-1, 806-2, and 806-3).

In some embodiments, the background extends to an edge of the display(e.g., 810).

In some embodiments, the background includes a first portion occupying afirst half of the display and a second portion occupying a second halfof the display (e.g., 810-1 and 810-2).

In some embodiments, the boundary between the first portion and thesecond portion is a straight line (e.g., 812).

In some embodiments, the boundary is along the first clock hand (e.g.,806-1 of FIGS. 8A-8D).

In some embodiments, the first portion includes a first color or visualpattern and the second portion includes a second color or visual patterndifferent than the first color or visual pattern (e.g., 810-1 and810-2).

At block 904, the device displays the watch user interface (e.g., 801)on the display (e.g., 602) at a second time after the first time (e.g.,FIG. 8B, second time of approximately 12:00:57). The watch userinterface at the second time includes the first clock hand (FIG. 8B,806-1) in a second position overlaid on the background (e.g., 810), thebackground having a second graphical characteristic at the second timethat is determined based on the second position of the first clock hand(e.g., 810 of FIG. 8A and 810 of FIG. 8B).

Dynamically modifying a characteristic of the background of a watch userinterface based on the position of a clock hand provides the user withan easily decipherable visual indication of the current time measured bythe watch. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to quickly resolve informationdisplayed, the user does not need to spend as much time interacting withthe device) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device moreefficiently.

In some embodiments, displaying the watch user interface on the displayat the first time further includes displaying a graphical element at afifth position and displaying the watch user interface on the display atthe second time further includes displaying the graphical element at thefifth position (e.g., 808).

In some embodiments, the difference between the first graphicalcharacteristic at a first time and the second graphical characteristicat a second time corresponds to a rotation of the background relative toa physical frame of the device (e.g., 810 of FIG. 8B and 810 of FIG.8A). In some embodiments, the physical frame (e.g., 603) includes arotatable input mechanism (e.g., 604) and/or a button (e.g., 605).

In some embodiments, the first clock hand and the background rotatearound a common origin (e.g., 806-1 and 810 FIGS. 8A-8H).

In some embodiments, the shape of the first portion at the first time isdifferent than the shape of the first portion at the second time (e.g.,810-1 of FIG. 8A and 810-1 of FIG. 8B) (e.g., the shapes are “triangles”when the boundary goes from corner to corner and are “rectangles” whenthe boundary is vertical or horizontal (corners of display are rounded,so shapes are not true triangles and rectangles).

Dynamically modifying the shape of the portions which make up thebackground of a watch user interface based on the position of a clockhand provides the user with an easily decipherable visual indication(e.g., a bold dynamically change shape) of the current time measured bythe watch. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to quickly resolve informationdisplayed, the user does not need to spend as much time interacting withthe device) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device moreefficiently.

In some embodiments, the first graphical characteristic at the firsttime includes a visual indication of the hour of the first time (e.g.,FIG. 8J, 814 indicating hour 10 of time 10:15:35), and wherein thesecond graphical characteristic at the second time includes a visualindication of the hour of the second time (e.g., FIG. 8I, 814 indicatinghour 12 of time 12:00:57). In some embodiments, the graphicalcharacteristic includes a spotlight effect that follows the hour hand(e.g., the end of the hour hand).

Dynamically modifying the background of a watch user interface toinclude a spotlight on the current hour indicator based on the positionof a clock hand provides the user with an easily decipherable visualindication that quickly draws the user attention to relevant information(e.g., the current hour measured by the watch). Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to quickly resolve information displayed, the user does not need tospend as much time interacting with the device) which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more efficiently.

In some embodiments, the watch user interface, at the first time and atthe second time, is configured to display one or more characteristics ofthe background in accordance with the position of the first clock hand.Optionally, at block 906, the device receives a sequence of one or moreuser inputs corresponding to a request to display the one or morecharacteristics of the background in accordance with the position of asecond clock hand (e.g., a change in a background characteristicconfiguration from the first hand to the second hand), different thanthe first clock hand (e.g., 806-2 of FIGS. 8E-8H). In some embodiments,the sequence of one or more user inputs includes a contact with thedisplay (e.g., 602) having a characteristic intensity above an intensitythreshold, which causes the electronic device (e.g., 600) to enter awatch face edit mode or a watch face settings edit mode.

Enabling the user to change the hand that dictates how thecharacteristic of the background of a watch user interface changes overtime provides the user with feedback indicating to them how a specificunit of time is being measured by the watch via an easily decipherablevisual indication. Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to quickly resolveinformation displayed, the user does not need to spend as much timeinteracting with the device) which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more efficiently.

In some embodiments, the second clock hand (e.g., 806-2) has a rate ofmovement different than the rate of movement of the first clock hand(e.g., the first clock hand is an hour hand and the second clock hand isa minute hand, the minute hand having rate of movement greater than therate of movement of the hour hand).

In some embodiments, the second clock hand is one of an hour hand (e.g.,806-1), a minute hand (e.g., 806-2), or a second hand (e.g., 806-3).

After receiving the sequence of one or more user inputs at block 906,optionally, at block 908, the device displays the watch user interface(e.g., 810) on the display at a third time (e.g., FIG. 8E). The watchuser interface (801) at the third time includes the second clock hand ina third position (806-2 of FIG. 8E) overlaid on the background, thebackground having a third graphical characteristic at the third timethat is determined based on the third position of the second clock hand(e.g., 810 of FIG. 8E).

Optionally, at block 910, the device displays the watch user interface(e.g., 801) on the display (e.g., 801) at a fourth time (e.g., FIG. 8F)after the third time (e.g., FIG. 8E). The watch user interface at thefourth time includes the second clock hand in a fourth position (e.g.,806-2 of FIG. 8F) overlaid on the background and the background has afourth graphical characteristic at the fourth time that is determinedbased on the fourth position of the second clock hand (e.g., 810 of FIG.8F).

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9) are also applicable in an analogous manner tothe methods described above (e.g., 700) and below (e.g., 1100). Forexample, method 700 optionally includes one or more of thecharacteristics of the various methods described above with reference tomethod 900. For example, the background of clock face 606 in FIG. 6A canbe divided into two portions and change dynamically based on theposition of hour hand 616-1 in a manner analogous to techniquesdescribed with reference to method 900. For brevity, these details arenot repeated below.

FIGS. 10A-10T illustrate exemplary watch user interfaces, in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the methods in FIGS.11A-11D.

FIG. 10A illustrates device 600 as described above. As illustrated inFIG. 10A, device 600 displays watch user interface 1000 on display 602.Watch user interface 1000 includes an indication of time having hourhand 1006-1, minute hand 1006-2, and second hand 1006-3. Watch userinterface 1000 also includes weather complication 1008-1, heart ratecomplication 1008-2, and date complication 1008-3. Weather complication1008-1 displays data from a weather application, including a singlemetric, current temperature 1010. Heart rate complication 1008-2 isassociated with a heart rate application, as indicated by the heart iconincluded in the complication. Heart rate complication 1008-2 does notinclude a metric related to data from the heart rate application. Datecomplication 1008-3 provides date information including day of the week1012 and day of the month 1014.

FIG. 10B illustrates an enhanced watch user interface 1002 displayed ondisplay 602. Enhanced watch user interface 1002 includes an enhancedversion of weather complication 1008-1′, an enhanced version of heartrate complication 1008-2′, and date complication 1008-3. As illustratedin FIG. 10B, weather complication 1008-1′, heart rate complication1008-2′, and date complication 1008-3 are the same size as weathercomplication 1008-1, heart rate complication 1008-2, and datecomplication 1008-3 on watch user interface 1000. Weather complication1008-1′ and heart rate complication 1008-2′ are enhanced in the sensethat they include additional information or metrics related to data fromtheir respective applications than weather complication 1008-1 and heartrate complication 1008-2 displayed on watch user interface 1000. Weathercomplication 1008-1′ and heart rate complication 1008-2′ also havehigher resolution (e.g., smaller text size, smaller feature sizes (e.g.,degree symbol), and/or larger range of colors or greyscale) than weathercomplication 1008-1 and heart rate complication 1008-2 displayed onwatch user interface 1000.

In some embodiments, enhanced weather complication 1008-1′ and enhancedheart rate complication 1008-2′ are displayed in accordance with thewatch user interface being enhanced watch user interface 1002 (e.g.,instead of “regular” watch user interface 1000). For example, inresponse to a selection (e.g., by a user or based on a default setting)to display a complication associated with a weather application ondisplay 602, device 600 displays weather complication 1008-1 inaccordance with the watch user interface being watch user interface1000, whereas device 600 displays enhanced weather complication 1008-1′in accordance with the watch user interface being enhanced watch userinterface 1002. Similarly, a request to display a heart ratecomplication results in display of enhanced heart rate complication1008-2′ on enhanced watch user interface 1002 and display of heart ratecomplication 1008-2 on watch user interface 1000.

As illustrated in FIG. 10B, enhanced weather complication 1008-1′,enhanced heart rate complication 1008-2′, and date complication 1008-3each includes two or more metrics related to data from a respectiveapplication. Enhanced weather complication 1008-1′ includes currenttemperature 1010, temperature range 1026, and relative currenttemperature indicator 1028, which indicates the relative position ofcurrent temperature 1010 within temperature range 1026. Enhanced heartrate complication 1008-2′ includes current (or most recently measured)beats per minute 1020, daily low beats per minute 1022, and daily highbeats per minute 1024. Date complication 1008-3 includes day of the week1012 and day of the month 1014.

As illustrated in FIG. 10C, device 600 receives (e.g., detects) userinput 1081 (e.g., a tap) corresponding to a request to edit enhancedwatch user interface 1002. As illustrated in FIG. 10D, in response touser input 1081, device 600 enters an edit mode (e.g., watch face editmode or complication edit mode) and visually distinguishes datecomplication 1008-3 for editing (e.g., by displaying box 1036 arounddate complication 1008-3 and label 1038 identifying the associatedapplication). In some embodiments, device 600 visually distinguishes thecomplication selected for editing (e.g., date complication 1008-3) byvarying one or more visual properties (e.g., brightness, opacity, color,contrast, hue, saturation, etc.) of watch user interface 1002, orportions thereof. In some embodiments, while in edit mode, thecomplication selected for editing is displayed with a first visualproperty (e.g., in color or a plurality of colors other than greyscale)and one or more other complications (e.g., all other complications) aredisplayed with a second visual property (e.g., in greyscale or in asingle color different from the plurality of colors that thecomplication would otherwise be displayed in when the device is not inthe edit mode) even though, in some embodiments, some or all of theother complications are displayed in one or more colors in the watchface when the watch face is displayed while the device is not in theedit mode. For example, complication 1008-3 is displayed in color andcomplications 1008-2 and 1008-1 are displayed in greyscale. In someembodiments, while in edit mode, a visual property of one or more of theunselected complications is changed (e.g., a brightness or opacity ofone or more of the unselected complications is reduced to distinguishthe unselected complications from the selected complication) instead of,or in addition to, the change to the visual property of the one or moreselected complications. In some embodiments, the visual distinguishingof the selected complication is instead of or in addition to analternative selection indicator such as a selection ring around at leasta portion of the selected complication. While in edit mode, device 600also displays complication menu bar 1032 with complication positionindicator 1034, which indicates the position of the currently displayedcomplication within a menu of complications available for selection. Insome embodiments, user input 1081 includes a contact having acharacteristic intensity and device 600 enters the edit mode inaccordance with a determination that the characteristic intensityexceeds a predetermined threshold intensity.

As illustrated in FIG. 10E, device 600 receives (e.g., detects) userinput 1083, which includes rotation of rotatable input mechanism 604. Insome embodiments, user input 1083 is received at a device other thandevice 600 through a companion application which communicates withdevice 600. As illustrated in FIG. 10F, in response to receiving (e.g.,detecting) user input 1083, device 600 displays a representation of windcomplication 1008-4 to add to enhanced watch user interface 1002 inplace of date complication 1008-3. Device 600 updates complicationposition indicator 1034 to indicate that wind complication 1008-4 islocated near the bottom of the complication menu (e.g., because thecomplications are in alphabetical order and “w” is near the end of thealphabet). Wind complication 1008-4 includes metrics wind speed 1040 (22mph) and wind direction 1042 (northeast). In some embodiments, windcomplication 1008-4 is not available for selection on other watch userinterfaces (e.g., watch user interface 1000).

As illustrated in FIG. 10G, device 600 receives (e.g., detects) userinput 1085 (e.g., a tap) corresponding to selection of enhanced heartrate complication 1008-2′. As illustrated in FIG. 10H, in response toreceiving (e.g., detecting) user input 1085, device 600 visuallydistinguishes enhanced heart rate complication 1008-2′ for editing. Insome embodiments, in response to receiving user input 1085, device 600transitions from visually distinguishing a first complication forediting (e.g., wind complication 1008-4) to visually distinguishing asecond complication for editing (e.g., heart rate complication 1008-2)by varying one or more visual properties (e.g., brightness, color,contrast, hue, saturation, etc.) of watch user interface 1002, orportions thereof. For example, in response to receiving user input 1085,device 600 transitions from displaying complication 1008-4 in color andcomplications 1008-2 and 1008-1 in greyscale to displaying complication1008-2 in color and complications 1008-4 and 1008-1 in greyscale. Insome embodiments, while in edit mode, a visual property of one or moreof the unselected complications is changed (e.g., a brightness oropacity of one or more of the unselected complications is reduced todistinguish the unselected complications from the selectedcomplication). In some embodiments, the visual distinguishing of thesecond complication is instead of or in addition to an alternativeselection indicator such as a selection ring around at least a portionof the second complication. As illustrated in FIG. 10I, device 600receives (e.g., detects) user input 1087, which includes rotation ofrotatable input mechanism 604. As illustrated in FIG. 10J, in responseto receiving (e.g., detecting) user input 1087, device 600 displays arepresentation of humidity complication 1008-5 to add to enhanced watchuser interface 1002 in place of enhanced heart rate complication1008-2′. Humidity complication 1008-5 includes metrics current humidity1054, humidity range 1050, and relative current humidity indicator 1052.In some embodiments, humidity complication 1008-5 is not available inother watch user interfaces (e.g., watch user interface 1000).

A user can similarly request to add a new complication in place ofenhanced weather complication 1008-1′ by selecting enhanced weathercomplication 1008-1′ (e.g., with a tap) in edit mode and movingrotatable input mechanism 604 to select the new complication.

As illustrated in FIG. 10K, device 600 receives (e.g., detects) userinput 1089. As illustrated in FIG. 10L, in response to receiving (e.g.,detecting) user input 1089, device 600 exits edit mode and displaysenhanced watch user interface 1002 with selected complications windcomplication 1008-4 and humidity complication 1008-5, and previouslydisplayed enhanced weather complication 1008-1′. In some embodiments,enhanced weather complication 1008-1′, wind complication 1008-4, andhumidity complication 1008-5 all display data from the same weatherapplication, thus providing three complications related to the sameapplication, with each complication including at least two metrics notprovided by either of the other two complications. FIG. 10L alsoillustrates an embodiment of a watch user interface with three gaugecomplications, each providing a parameter value and either high and/orlow values or a direction (e.g., wind direction).

In some embodiments, date complication 1008-3 is replaced with humiditycomplication 1008-5 at FIGS. 10D and 10E resulting in an enhanced watchuser interface including three complications, each having three metrics(e.g., humidity complication 1008-5 (current humidity, low humidity, andhigh humidity), enhanced heart rate complication 1008-2′ (current heartrate, low heart rate, and high heart rate), and enhanced weathercomplication 1008-1′ (current temperature, low temperature, and hightemperature)).

In some embodiments, instead of replacing date complication 1008-3 andenhanced heart rate complication 1008-2′, a user can replace a singlecomplication (e.g., by exiting edit mode after user input 1083 in FIG.10E), in which case device 600 maintains display of the othercomplications (e.g., enhanced heart rate complication 1008-2′ andenhanced weather complication 1008-1′). Similarly, enhanced heart ratecomplication 1008-2′ can be replaced while maintaining display of (e.g.,without replacing) data complication 1008-3 and enhanced weathercomplication 1008-1; and enhanced weather complication 1008-1 can bereplaced while maintaining display of (e.g., without replacing) enhancedheart rate complication 1008-2′ and data complication 1008-3.

In some embodiments, elements of enhanced watch user interface 1002,such as hands 1006 and non-selected complications, are not modified(e.g., remain unchanged) while replacing the selected complication(s).

Turning now to FIG. 10M, watch user interface 1091 includescomplications 1060-1, 1060-2, and 1060-3, each including metrics relatedto data from a world clock application for a respective location (e.g.,Moscow, Beijing, and London), a time associated with the location (e.g.,an analog clock face with hour and minute hands), and an indication ofday, night, sunset, or sunrise (e.g., complication 1060-1 indicates thatit is night in Moscow and complication 1060-2 indicates that it is dayin Beijing). In some embodiments, one or more of complications 1060-1,1060-2, or 1060-3 includes an offset to local time. As illustrated inFIG. 10M, the position of the location indicator (e.g., BEI 1056) withinthe complication is based on the position of hands 1058. In someembodiments, the location indicator is positioned not to overlap orinterfere with the clock hands. For example, location indicators LON andBEI are positioned in the center-top of complications 1060-3 and 1060-2,respectively, and do not interfere with their respective clock hands. Incomplication 1060-1, location indicator MOS is positioned in thecenter-bottom of the complication since it would overlap with the hourhand if positioned in the center-top position of LON and BEI. In someembodiments, the position of the location indicator changes over time toavoid interfering with the clock hands as they move.

FIG. 10N illustrates an embodiment of a watch user interface with threecomplications related to a calendar application. Complication 1070-1includes an affordance that can be selected to initiate a process forcreating a new event in the calendar application. Complication 1070-2includes metrics related to data from the calendar application,including time of an event (6 PM), subject or event name (DINNER), andlocation (SF). Complication 1070-3 is a date complication that includesa day of the week and a day of the month.

FIG. 10N also illustrates an embodiment of a complication with a visualcharacteristic at or around a ring-shaped area (“the numeral ring”) onwatch user interface 1093. Watch user interface 1093 has a ring-shapedarea on the clock face that includes the hour numerals (1-12), where thering-shaped area has a curved outer edge. In some embodiments, thering-shaped area includes tick marks indicating hours and/or minutes ornumeric minute markers. In accordance with an application correspondingto a particular application (e.g., calendar, weather, exercise, heartrate, breathe, stocks), device 600 displays a visual characteristic ator around the ring-shaped area. For example, in accordance with acomplication being associated with a calendar application, device 600displays a complication with event name 1064 and event location 1066around the ring-shaped area of watch user interface 1093 (e.g., eventname 1064 and event location 1066 follow the outer edge of the clockface). Alternatively, in accordance with a complication being associatedwith another application (e.g., battery, digital time, date, orstopwatch), device 600 forgoes displaying a visual characteristic at oraround the ring-shaped area.

FIG. 10O illustrates an embodiment of a watch user interface with threecomplications with data from a stocks application. Stock complications1078-1, 1078-2, and 1078-3 including metrics related to data from thestocks application, including ticker symbol 1076 (e.g., stock name),price 1074, and direction of movement 1075.

FIG. 10P illustrates an embodiment of corner complication displayed inthe lower-right corner of watch user interface 1097 between the edge ofthe numeral ring and the lower and right edges and lower-right corner ofdisplay 602. The corner complication is a temperature complication thatincludes status bar 1082 (representing a temperature range), statusindicator 1084 (representing the relative position of a currenttemperature within the temperature range), and current status 1086(representing the current temperature). Status bar 1082 tracks the outeredge of the numeral ring and current status 1086 is located betweenstatus bar 1082 and the lower-right corner of display 602.

FIG. 10Q illustrates a target complication 1088-3 that displays metricsrelated to data from a health application. Target complication 1088-3includes current value 1098 of a metric (e.g., floors climbed) andprogress indicator 1090 indicating the amount of progress made towards atarget value or goal. Progress indicator 1090 includes a ring thatsurrounds slightly more than half of the outer edge of complication1088-3, which indicates that the current value of 67 represents slightlymore than 50 percent progress towards a target value or goal. Otherexemplary target complications include a battery complication includingtotal battery capacity and current charge state, a health complicationincluding a current value of steps, standing hours, or calories burnedor consumed and progress toward a target or goal for steps, standinghours, or calories burned or consumed, respectively.

FIG. 10Q also illustrates air quality index (AQI) complication 1088-1,which includes a current AQI value 1094 and a relative status indicator1096 representing the position of current AQI value 1094 relative to arange (e.g., good to hazardous). In some embodiments, AQI complication1088-1 can be represented as a target complication, with a low AQI valuebeing a target or goal.

FIGS. 10R-10T illustrate watch user interfaces including digitalindication time 1006-4 (e.g., 10:09), compact date indicator 1009 (e.g.,WED 29), and three or more complications displaying metrics related todata from a single application.

As illustrated in FIG. 10R, watch user interface 1003-1 includes fivecomplications with data from a weather application. As described above,air quality index (AQI) complication 1004-1 includes a current airquality value and a relative status indicator and wind complication1004-2 includes a wind speed and a wind direction. UV complication1004-3 includes a current UV index value 1007-1, relative statusindicator 1007-2 representing the position of current UV index value1007-1 relative to a range (e.g., good to hazardous), and visualindication of the UV condition 1007-3 (e.g. a sun graphic indicating amoderate to high current UV index value).

As illustrated in FIG. 10R, weather chart complication 1004-4 includestextual weather label 1005-1 displaying a respective location (e.g.,Cupertino) and current temperature at the respective location (e.g., 72)and temperature chart 1005-2. Temperature chart 1005-2 includes a firstaxis (e.g., hours) and a second axis (e.g., temperature), bar graph data1005-3 representing the temperature price at the respective location(e.g., Cupertino) over a fixed period time, and current temperatureindicator 1005-5 (e.g. a visually distinguished bar within the bar graphdata corresponding to the current time of day). Bar graph data 1005-3includes vertical bars at fixed intervals representing actual orforecasted temperature at the corresponding time on the first axis(e.g., time axis). In some embodiments, the scale of the first or thesecond axis is adjusted to reflect a desired range of temperature valuesor desired time scale for displaying temperature (e.g., the first axisreflects a period of 1-hour, 12-hours, 1-day, etc.). Weather iconcomplication 1004-5 includes a weather condition icon visuallyrepresenting a current or forecasted weather condition (e.g., graphicillustrating partly cloudy weather).

Turning now to FIG. 10S, watch user interface 1003-2 includescomplications 1016-1, 1016-2, 1016-3, and 1016-4. Complications 1016-1,1016-2, and 1016-3, each include metrics related to data from a worldclock application for a respective location (e.g., New York, London, andHong Kong), a time associated with the location (e.g., an analog clockface with hour and minute hands), and an indication of day, night,sunset, or sunrise (e.g., complication 1016-1 indicates that it is dayin New York and complication 1016-2 indicates that it is night inLondon). In some embodiments, one or more of complications 1016-1,1016-2, or 1016-3 includes an offset to local time. As described inreference to FIG. 10M above, the position of the location indicator(e.g., NYC) within the corresponding complication is based on theposition of hands (e.g., the location indicator is positioned not tooverlap or interfere with the clock hands and changes over time to avoidinterfering with the clock hands as they move).

As illustrated in FIG. 10S, stock complication 1016-4 includes metricsrelated to data from a stock application including stock label 1017-1indicating a respective stock (e.g. APPL), price indicator 1017-2displaying a current price and direction of price movement for therespective stock (e.g., APPL is at 178.14 and rising) and stock chart1017-3. Stock chart 1017-3 includes first axis (e.g., relative price),second axis (e.g., time), price line 1017 indicating the price of therespective stock (e.g., APPL) over time, and current price indicator1017-5 (e.g. vertical bar intersecting price line 1017-4 at a time onthe second axis corresponding to a current time). In some embodiments,the scale of the first or the second axis is adjusted to reflect adesired time scale or value range for displaying the price of therespective stock (e.g., the first axis reflects a period of 1-day,1-week, 1-month, 3-months, 6-months, 1-year, the year-to-date and thesecond axis reflects percent change, absolute change, or measure pricein various fiat or cryptographic currencies).

Turning now to FIG. 10T, watch user interface 1003-3 includes twocomplications with data from an activity application. Activity chartcomplication 1018-1 includes textual activity label 1019-1 displayingcalories burned (e.g., 350), minutes exercised (e.g., 11), and standinghours (e.g., 06), and activity chart 1019-2. Activity chart includes atime axis 1019-3 (e.g., hours), active minutes scale 1019-4, caloriescale 1019-5, and chart data 1019-6 representing the accrual of activitymetrics over the discrete periods displayed on time axis 1019-3 (e.g.,amounts of active minutes and calories burned for a given time periodare represented as vertical bars of proportional height on theirrespective scales and standing hours are represented by circularindicators). Compact activity complication 1018-2 is includes agraphical element displaying progress towards multiple activity-relatedfitness goals (e.g., an icon illustrating progress toward caloric burn,active time, and standing hours goals in concentric circular bands).

As illustrated in FIG. 10T, watch user interface 1003-3 also includesthree complications associated with three distinct applications otherthan an activity application. Breathe complication 1018-3 is associatedwith a breathe application (e.g., a meditation or mindfulnessapplication), as indicated by the breathe icon included in thecomplication. Heart rate complication 1018-4 is associated with a heartrate application, as indicated by the heart icon included in thecomplication. Workout complication 1018-5 is associated with a workoutapplication, as indicated by the workout icon included in thecomplication. Complications 1018-3, 1018-4, and 1018-5 do not includemetrics related to data from the respective applications.

In some embodiments, device 600 allows a user to select from two or morewatch user interfaces that each have three complications with data fromthe same application (e.g., a “collection” of complications). Forexample, in some embodiments, device 600 provides a user with acapability to select from two or more of watch user interfaces 1091(FIG. 10M), 1093 (FIG. 10N), 1095 (FIG. 10O), 1097 (FIG. 10P), 1099(FIG. 10Q), 1003-1 (FIG. 10R), 1003-2 (FIG. 10S), and 1003-3 (FIG. 10T).In some embodiments, while displaying one of watch user interfaces 1091(FIG. 10M), 1093 (FIG. 10N), 1095 (FIG. 10O), 1097 (FIG. 10P), 1099(FIG. 10Q), 1003-1 (FIG. 10R), 1003-2 (FIG. 10S), and 1003-3 (FIG. 10T),device 600 detects a sequence of one or more inputs that corresponds toselection of another one of watch user interfaces 1091 (FIG. 10M), 1093(FIG. 10N), 1095 (FIG. 10O), 1097 (FIG. 10P), 1099 (FIG. 10Q), 1003-1(FIG. 10R), 1003-2 (FIG. 10S), and 1003-3 (FIG. 10T). In response todetecting the sequence of one or more inputs, device 600 displays theselected watch user interface.

FIGS. 11A-11D are a flow diagram illustrating a method for providingcontext-specific user interfaces using an electronic device inaccordance with some embodiments. Method 1100 is performed at a device(e.g., 100, 300, 500, or 600) with a display. Some operations in method1100 are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 1100 provides an intuitive way forconfiguring context-specific user interfaces. The method reduces thecognitive burden on a user, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to configure context-specific user interfaces. fasterand more efficiently conserves power and increases the time betweenbattery charges.

At block 1102, the device displays a watch user interface (e.g., 1000 ofFIG. 10A) on the display (e.g., 602). The watch user interface includesa first complication (e.g. 1008-1) that includes at least a first metricrelated to data from a first application (e.g., 1010 of FIG. 10A-10C)and a second metric related to data from the first application (e.g.,1026 of FIG. 10A-10C). In some embodiments, a complication refers to anyclock face feature other than those used to indicate the hours andminutes of a time (e.g., clock hands or hour/minute indications). Insome embodiments, complications provide data obtained from anapplication. In some embodiments, a complication includes an affordancethat when selected launches a corresponding application (e.g., 1008-2 ofFIG. 8A). In some embodiments, a complication is displayed at a fixed,predefined location on the display.

In some embodiments, the first complication includes an analog clockface having one or more hands indicating a time at a geographic locationand text indicating the geographic location (e.g., 1060), wherein thetext indicating the geographic location is positioned on thecomplication based on the position of the one or more hands (e.g.,1058). In some embodiments, the complication is positioned to avoidoverlapping with the one or more hands of the clock face (e.g., FIG.10M).

Automatically moving a textual description on a clock face to avoidbeing obstructed by the clock hands as they progress around the dialthroughout the day provides the user with more reliable visual feedbackabout time of being displayed by the clock and the location which thattime represents. Providing improved visual feedback to the user enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to quickly and accurately resolveinformation displayed, the user does not need to spend as much timeinteracting with the device) which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more efficiently.

Further, at block 1102, the device displays a second complication (e.g.,1008-2) that includes at least a third metric related to data from asecond application (e.g., 1020) and a fourth metric related to data fromthe second application (e.g., 1022), and a third complication (e.g.,1008-3) that includes at least a fifth metric related to data from athird application (e.g., 1012) and a sixth metric related to data fromthe third application (e.g., 1014). In some embodiments, the secondapplication is different than the first application (e.g., FIG.10A-10I). In some embodiments, the second application is the same as thefirst application, but the third and fourth metrics are different thanthe first and second metrics (e.g., FIGS. 10J-10Q). In some embodiments,the third application is different than the first and/or secondapplication (e.g., FIG. 10A-10E). In some embodiments, the thirdapplication is the same as the first and second applications, but thefifth and sixth metrics are different than the first, second, third, andfourth metrics (e.g., FIG. 10K-10L).

Automatically grouping the display of related metrics at multiplelocations on an interface provides the user an efficient way of locatingrelevant information and deciphering data from multiple applicationsprovide by the device. The added context provided by the visual groupingprovides the user with feedback regarding how displayed data should beinterpreted, thereby enhancing the operability of the device and makingthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device, increasing the speed a user caninterpret data) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device moreefficiently.

In some embodiments, the first complication further includes a ninthmetric related to data from the first application (e.g., 1088-1), thesecond complication further includes a tenth metric related to data fromthe second application (e.g., 1008-2 of FIGS. 10B-10I), and the thirdcomplication each further includes an eleventh metric related to datafrom the third application (e.g., 1008-4). In some embodiments, thefirst, second, or third complication is a humidity complication (e.g.,1008-5, including current humidity, low humidity, and high humidity), aheart rate complication (e.g., 1008-2, including current heart rate, lowheart rate, and high heart rate), or a weather complication (e.g.,1008-1, including current temperature, low temperature, and hightemperature).

In some embodiments, the first application, the second application, andthe third application are the same application (e.g., FIGS. 10J-10T).

In some embodiments, the first application is different than the secondapplication, and the third application is different than the firstapplication and the second application (e.g., FIG. 10A-10E).

In some embodiments, the watch user interface (e.g., 1093) furtherincludes a clock face having a curved outer edge and a curvedcomplication having a visual feature that follows the outer edge of theclock face (e.g., FIG. 10N).

Automatically presenting information in a manner that conforms to theouter edge of the clock face provides the user with enhanced visualfeedback by keeping the user interface less cluttered. This enables theuser focus their attention on fewer visual elements and as a result,more rapidly locate relevant information throughout the interface andinteract more accurately with intended controls features on the display.This enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user more quicklylocation information, and more accurately provide proper inputs andreducing user mistakes when operating/interacting with the device),which additionally reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the watch user interface (e.g., 1097) furtherincludes a ring-shaped area having a curved outer edge and a cornercomplication, a status bar that tracks the outer edge of the ring-shapedarea (e.g., 1082), and a value (e.g., 1086) located between the statusbar and a corner of the display (e.g., FIG. 10P).

In some embodiments, the first metric and the second metric relate todata from a clock application, the first metric representing ageographic location and the second metric representing a time associatedwith the geographic location (e.g., 1060). In some embodiments, thefirst and the second metric represent other clock data (e.g., an offsetto local time, or indications of sunset and sunrise times).

In some embodiments, the first metric and the second metric relate todata from a calendar or date application (e.g., FIG. 10N), the firstmetric representing an event and the second metric representing a timeassociate with the event (e.g., 1070-2). In some embodiments, the firstand second metrics represent other data (e.g., a location of the event).

In some embodiments, the first metric and the second metric relate todata from a stocks application (e.g., 1078 of FIG. 10O), the firstmetric representing a stock name, and the second metric representing anassociated stock price. In some embodiments, the first and secondmetrics represent other data (e.g., a direction of price movement, apercent change in price, etc.).

In some embodiments, the first metric and the second metric relate todata from a weather application (e.g., 1008-1), the first metricrepresenting a current temperature (e.g., 1010), and the second metricrepresenting forecasted high and low temperatures (e.g., 1026). In someembodiments, the first and second metrics represent other data, e.g.,humidity, wind speed and direction, a visual depiction of weatherconditions, etc., and forecasted values thereof (e.g., FIG. 10J-10L).

In some embodiments, the first complication includes a visualrepresentation of one or more metrics, the visual representationincluding an indication of a value relative to a range of values (e.g.,1088-1 and 1088-3). In some embodiments, the complication displays atarget value and progress toward that value (e.g., 1090) (e.g., totalbattery capacity and current charge state, air quality, and varioushealth or fitness metrics including progress toward step, floors climb,standing hours, and caloric goals). In some embodiments, thecomplication displays one or more metrics (e.g., current values and highand low values for a parameter) on a gauge which represents data from anapplication (e.g., a weather application including temperature,humidity, wind speed, etc.).

In some embodiments, the first complication includes a visualrepresentation of one or more metrics, the visual representationincluding a first affordance representing a simulation of a first regionof the Earth as illuminated by the Sun at a current time, the methodfurther comprising: detecting a sequence of one or more user inputscorresponding to a request to view the simulation of the Earth at anon-current time; and in response to detecting the sequence of one ormore user inputs corresponding to a request to view the simulation ofthe Earth at a non-current time, rotating the simulation of the Earth toreveal a second region of the Earth as illuminated by the Sun at thenon-current time. In some embodiments, the sequence of one or moreinputs includes an input corresponding to selection of the firstcomplication, which causes device 600 to launch an astronomy applicationdisplaying an interactive simulation of the Earth as illuminated by theSun at a current time. In response to an input (e.g., a swipe) on thesimulation of the Earth within the astronomy application, the devicerotates the simulation of the Earth to reveal a region of the Earth asilluminated by the Sun at the current time (e.g., 608-2).

A visual representation of the earth as illuminated by the Sun providesthe user with a rapid means of determining a large quantity ofinformation (e.g., time of day, geographic location, season, relativeday time and night time, etc.) without cluttering the interface withexcess textual elements. This enables the user to more rapidly locaterelevant information throughout interface and access intended controlsmore quickly and accurately. This enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser more quickly location information, and more accurately provideproper inputs and reducing user mistakes when operating/interacting withthe device), which additionally reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

At block 1104, the device detects a sequence of one or more inputs(e.g., 1081 and 1083) that correspond to a request to add a fourthcomplication (e.g., 1008-4) to the watch user interface (e.g., 1002 ofFIG. 10C-10E). The fourth complication includes at least a seventhmetric related to data from a fourth application (e.g., 1040) and aneighth metric related to data from the fourth application (e.g., 1042).

At block 1106, in response to detecting the sequence of one or moreinputs, the device performs the operation of block 1108, block 1110, orblock 1112. At block 1108, in accordance with a determination that thesequence of one or more inputs corresponds to a request to replace thefirst complication, the device replaces the first complication with thefourth complication (e.g., FIG. 10F). At block 1110, in accordance witha determination that the sequence of one or more inputs (e.g., 1082)correspond to a request to replace the second complication, the devicereplaces the second complication with the fourth complication (e.g.,FIG. 10H). At block 1112, in accordance with a determination that thesequence of one or more inputs correspond to a request to replace thethird complication, the device replaces the third complication with thefourth complication.

Optionally, at block 1114, in accordance with a determination that thesequence of one or more inputs corresponds to a request to replace thefirst complication, the device maintains the second complication and thethird complication (e.g., FIG. 10F). Optionally, at block 1116, inaccordance with a determination that the sequence of one or more inputscorresponds to a request to replace the second complication, the devicemaintains the first complication and the third complication (e.g., FIG.10H). Optionally, at block 1118, in accordance with a determination thatthe sequence of one or more inputs corresponds to a request to replacethe third complication, the device maintains the first complication andthe second complication. In some embodiments, the watch user interfaceincludes additional elements such as hands and additional complicationsthat are not modified while replacing the selected complication.

In some embodiments, the watch user interface (e.g., 1093) furtherincludes a ring-shaped area having a curved outer edge. In someembodiments, the clock face is an analog clock face having tick marks,hour markers (e.g., numbers), and/or minute markers (e.g., numbers)(e.g., 1072). Optionally, at block 1120, in accordance with the firstapplication corresponding to a fifth application, the devices devicedisplays a visual characteristic at or around the ring-shaped area(e.g., FIG. 10N). Optionally, at block 1122, in accordance with thefirst application corresponding to a sixth application different thanthe fifth application, the device forgoes displaying the visualcharacteristic at or around the ring-shaped area (e.g., FIG. 10M).

Optionally, at block 1124 the device displays a second watch userinterface. In some embodiments, the second watch user interface includesa fifth complication that includes less than two metrics related to datafrom the first application and is the same size as the firstcomplication (e.g., 1008-2 of FIG. 10A).

Collectively re-configuring a set of elements on a watch face to providea simplified interface in response to an input provides the user withmore control over the device by helping the user quickly configuremultiple display elements into a variety of configurations withoutrequiring individual interactions with each element. Reducing the numberof inputs need to perform equivalent operations, enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the fifth complication does not include a metricrelated to data from the first application (e.g., 1008-2 of FIG. 10A).

In some embodiments, the fifth complication has a lower resolution thanthe first complication on the watch user interface (e.g., 1008-1 and1008-1 of FIG. 10A).

In some embodiments, the watch user interface (e.g., 1091, 1093, 1095,1097, and 1099) is a first watch user interface, wherein the firstapplication, the second application, and the third application are thesame application (e.g., FIG. 10M-10Q). Optionally, while displaying thefirst watch user interface, at block 1126 the device detects a sequenceof one or more inputs that corresponds to selection of a second watchuser interface (e.g., FIG. 10A-10B).

Collectively re-configuring a set of elements on a watch face to providea themed interface directed at providing related information to the userprovides the user with more control over the device by helping the userquickly configure multiple display elements into a configuration thatincludes a variety of relevant information without requiring individualinteractions with each element. Reducing the number of inputs need toperform equivalent operations, enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device). Further, grouping relatedinformation for display makes it easier and therefore, more efficientfor the user to decipher displayed data. Each of these advantagesadditionally reduces power usage and improves battery life of the deviceby enabling the user to use the device more quickly and efficiently.

In response to detecting the sequence of one or more inputs thatcorresponds to selection of the second watch user interface, the deviceoptionally performs the operation of block 1128. At block 1128 thedevice displays the second watch user interface, wherein the secondwatch user interface (e.g., 1091, 1093, 1095, 1097, and 1099) whichincludes an eighth complication corresponding to a seventh application,a ninth complication corresponding to the seventh application, and atenth complication corresponding to the seventh application that isdifferent than the first application.

In some embodiments, the first complication includes a visualrepresentation of one or more metrics, the visual representationincluding a first affordance representing a simulation of a first regionof the Earth as illuminated by the Sun at a current time (e.g., 608-2).Optionally, at block 1130, the device detects a sequence of one or moreuser inputs corresponding to a request to view the simulation of theEarth at a non-current time. Optionally, at block 1132, in response todetecting the sequence of one or more user inputs corresponding to arequest to view the simulation of the Earth at a non-current time, thedevice rotates the simulation of the Earth to reveal a second region ofthe Earth as illuminated by the Sun at the non-current time. In someembodiments, the sequence of one or more inputs includes an inputcorresponding to selection of the first complication, which causesdevice 600 to launch an astronomy application displaying an interactivesimulation of the Earth as illuminated by the Sun at a current time. Inresponse to an input (e.g., a swipe) on the simulation of the Earthwithin the astronomy application, the device rotates the simulation ofthe Earth to reveal a region of the Earth as illuminated by the Sun atthe current time.

Note that details of the processes described above with respect tomethod 1100 (e.g., FIGS. 11A-11D) are also applicable in an analogousmanner to the methods described above (e.g., 700 and 900). For example,method 900 optionally includes one or more of the characteristics of thevarious methods described above with reference to method 1100. Forexample, watch user interface 801 of FIG. 8A can be configured toadditionally display three complications, including at least two metrics(e.g., complications 1008-1, 1008-2, and 1008-3 of FIG. 10A) overbackground 810, in a manner analogous to techniques described withreference to method 1100. For brevity, these details are not repeatedbelow.

FIGS. 12A-12R illustrate exemplary watch user interfaces, in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the methods in FIG.13.

FIG. 12A illustrates device 600 as described above. As illustrated inFIG. 12A, device 600 displays watch user interface 1200 on display 602.Watch user interface 1200 includes clock face 1202 surrounded by bezel1204. In FIG. 12A, clock face 1202 includes an indication of time havinghour hand 1206-1, minute hand 1206-2, and second hand 1206-3. Watch userinterface 1200 also includes workout complication 1208-1, musiccomplication 1208-2, timer complication 1208-3, and world clockcomplication 1208-4 (collectively “complications 1208”). Workoutcomplication 1208-1 is associated with a workout application, asindicated by the character icon included in the complication. Workoutcomplication 1208-1 does not include a metric related to data from theworkout application (e.g., workout complication 1208-1 only includes asingle icon). Music complication 1208-2 is associated with a musicapplication, as indicated by the musical note icon included in thecomplication, and displays data from the music application (e.g., timeremaining in a currently playing music file). Timer complication 1208-3displays data from a timer application, including elapsed time and/ortime remaining (e.g., timer data is displayed in numeral form and/orgraphically as a circular ring progressing radially along the insideedge of the complication at a rate proportional to the passage of time).World clock complication 1208-4 includes metrics related to data from aworld clock application, including a respective location (e.g., London)and a time associated with the location (e.g., an analog clock face withhour and minute hands). In FIG. 12A, complications 1208-1, 1208-2,1208-3, and 1208-4 occupy respective locations in the upper, right,lower, and left regions of the clock face 1202.

In FIG. 12A, watch user interface 1200 also includes cornercomplications 1212-1, 1212-2, 1212-3, and 1212-4 (collectively “cornercomplications 1212”), which occupy respective locations in theupper-right, lower-right, lower-left, and upper-left corners of watchuser interface 1200 (e.g., corner complication 1212-1 resides in theregion of watch user interface 1200 between the outer edge of bezel 1204and the corner formed by intersection of the upper and right edges ofdisplay 602). As described in reference to FIG. 10P above, cornercomplications 1212-1, 1212-2, and 1212-4 each display data related to arange of values associated with a metric from a correspondingapplication (e.g., temperature, humidity, air quality index (AQI), or UVindex from a weather application). Corner complication 1212-3 includesonly a single graphical element illustrating data from a weatherapplication (e.g., sunny sky conditions).

As illustrated in FIG. 12A, device 600 receives (e.g., detects) userinput 1290 (e.g., a long press on display 602) corresponding to arequest to edit watch user interface 1200. In response to user input1290, device 600 enters an edit mode (e.g., watch face edit mode orcomplication edit mode). In FIG. 12B, device 600 indicates edit mode byvisually distinguishing workout complication 1208-1 for editing (e.g.,by displaying box 1214 around workout complication 1208-1 and label 1216identifying the associated application). In some embodiments, device 600visually distinguishes the complication selected for editing (e.g.,workout complication 1208-1) by varying one or more visual properties(e.g., brightness, opacity, color, contrast, hue, saturation, etc.) ofwatch user interface 1200, or portions thereof. In some embodiments,while in edit mode, the complication selected for editing is displayedwith a first visual property (e.g., in color or a plurality of colorsother than greyscale) and one or more other complications (e.g., allother complications) are displayed with a second visual property (e.g.,in greyscale or in a single color different from the plurality of colorsthat the complication would otherwise be displayed in when the device isnot in the edit mode) even though, in some embodiments, some or all ofthe other complications are displayed in one or more colors in the watchface when the watch face is displayed while the device is not in theedit mode. For example, complication 1208-1 is displayed in color andcomplications 1208-2, 1208-3, and 1208-4 are displayed in greyscale. Insome embodiments, while in edit mode, a visual property of one or moreof the unselected complications is changed (e.g., a brightness oropacity of one or more of the unselected complications is reduced todistinguish the unselected complications from the selected complication)instead of, or in addition to, the change to the visual property of theone or more selected complications. In some embodiments, the visualdistinguishing of the selected complication is instead of or in additionto an alternative selection indicator such as a selection ring around atleast a portion of the selected complication. While in edit mode, device600 also displays complication menu bar 1218 with complication positionindicator 1220, which indicates the position of the currently displayedcomplication within a menu of complications available for selection. Insome embodiments, user input 1290 includes a contact having acharacteristic intensity and device 600 enters the edit mode inaccordance with a determination that the characteristic intensityexceeds a predetermined threshold intensity.

As illustrated in FIG. 12C, device 600 receives (e.g., detects) userinput 1292, which includes rotation of rotatable input mechanism 604. Insome embodiments, user input 1292 is received at another device thatcommunicates with device 600 (e.g., via a companion applicationassociated with device 600 running on the other device). In response toreceiving user input 1292, device 600 displays a representation ofcalendar complication 1208-5 to add to watch user interface 1200 inplace of workout complication 1208-1. In FIG. 12D, device 600 updatescomplication position indicator 1220 to indicate that calendarcomplication 1208-5 is located near the top of the complication menu(e.g., because the complications are in alphabetical order and “c” isnear the beginning of the alphabet). As illustrated in FIG. 12D, therepresentation of calendar complication 1208-5 includes indications ofthe type of information calendar complication 1208-5 will display onwatch user interface 1200 upon exiting the edit mode (e.g., current dayof week (WED), day of the month (23), and text describing the “NEXTAPPOINTMENT”).

In some embodiments, while in edit mode, the device receives (e.g.,detects) one or more inputs (e.g., a tap on display 602 or a press ofrotatable input mechanism 604) corresponding to a request to exit editmode. In response to exiting edit mode, device 600 adds calendarcomplication 1208-5 to watch user interface 1200, replacing workoutcomplication 1208-1 in the upper region of clock face 1202 and a portionof bezel 1204. As illustrated in FIG. 12E, calendar complication 1208-5includes two components, graphical element 1209 (e.g., illustrating thecurrent day of week and day of the month) and textual element 1210(e.g., a textual description of an upcoming calendar event). Asillustrated in FIG. 12E, graphical element 1209 is positioned on clockface 1202 closer to the center of display 602 than the inner edge ofbezel 1204, without overlapping with the area previously occupied bybezel 1204 (e.g., in the position previously occupied by complication1208-1 in the upper region of clock face 1202) and textual element 1210is positioned in a curved region along the edge of clock face 1202(e.g., in the position previously occupied by the top portion of bezel1204).

Automatically presenting content in a manner that utilizes differentareas of the display based on a content provides the user with enhancedvisual feedback by keeping the user interface less cluttered. Thisenables the user focus attention on fewer visual elements and as aresult, more rapidly locate relevant information throughout theinterface and interact more accurately with intended controls featureson the display. This enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user morequickly location information, and more accurately provide proper inputsand reducing user mistakes when operating/interacting with the device),which additionally reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

As illustrated in FIG. 12F, as time elapses, device 600 updates watchuser interface 1200. In FIG. 12F, the time displayed by hour hand 1206-1and minute hand 1206-2 displays a current time of 1:42:30 (formerly10:09:30 in FIG. 12E). In response to the passage of time, textualelement 1210 is updated to reflect the next event relative to thecurrent time (e.g., a meeting in the office at 3 PM) and the timedisplayed on world clock complication 1208-4 is updated to reflect thelocal time at the respective location (e.g., 09:42:30 in London). Asillustrated in FIG. 12F, the size of textual element 1210 is based onthe length of the associated content (e.g., the fewer number ofcharacters in the next appointment, the shorter the textual element andthe less of bezel 1204 is replaced).

Automatically adjusting the size of interface elements based on acontent provides the user with enhanced visual feedback by keeping theuser interface less cluttered. This enables the user focus theirattention on fewer visual elements and as a result, more rapidly locaterelevant information throughout the interface and interact moreaccurately with intended controls features on the display. This enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user more quickly location information,and more accurately provide proper inputs and reducing user mistakeswhen operating/interacting with the device), which additionally reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

As illustrated in FIG. 12G, device 600 receives (e.g., detects) userinput 1294 (e.g., a tap) on calendar complication 1208-5 (e.g., thegraphical element portion of complication 1208-5 or the textual elementportion occupying the region of watch user interface 1200 previouslyoccupied by bezel 1202). In response to receiving user input 1294,device 600 launches the application corresponding to calendarcomplication 1208-5 (e.g., a calendar application). As illustrated inFIG. 12H, upon launching the calendar application, watch user interface1200 is updated to display data from the calendar application includingdate element 1230, appointment time element 1232, appointmentdescription element 1234, and digital indication of time 1236. In someembodiments, device 600 receives (e.g., detects) user input 1294 (e.g.,a tap) in a location other than calendar complication 1208-5 and thedevice forgoes launching the calendar application.

Turning now to FIGS. 12I-12L, which illustrate embodiments of a watchuser interface including a heart rate complication. FIG. 12I illustrateswatch user interface 1200-2 at a first time (e.g., hour hand 1206-1 andminute hand 1206-2 indicating 10:42:30). Watch user interface 1200-2includes heart rate complication 1208-6 which includes graphical element1209 (e.g., a heart icon) and textual element 1210 (e.g., containingheart rate value 64 BPM and last reading value of “3 MIN AGO”).Graphical element 1209 is positioned closer to the center of display 602than the inner edge of bezel 1204.

FIG. 12J illustrates watch user interface 1200-2 at a later time (e.g.,hour hand 1206-1 and minute hand 1206-2 indicating 1:42:30). Watch userinterface 1200-2 includes heart rate complication 1208-6 displaying anupdated textual element 1210 (e.g., containing heart rate value 72 BPMand last reading value of “2 MIN AGO”). Watch user interface 1200-2 alsoincludes world clock complication 1208-4 with an indication of timeupdated corresponding to the change in time between FIG. 12I and FIG.12J.

Alternatively, as illustrated in FIGS. 12K-12L, device 600 displaysheart complication 1208-6 in a compact form (e.g., heart ratecomplication 1208-6 consists of a single graphical icon positioned onclock face 1202 closer to the center of display 602 than the inner edgeof bezel 1204).

FIGS. 12K-12N illustrate embodiments of a watch user interface includingan activity complication. FIG. 12K illustrates watch user interface1200-3 at a first time (e.g., hour hand 1206-1 and minute hand 1206-2indicating 10:42:30). Watch user interface 1200-3 includes activitycomplication 1208-7 which includes graphical element 1209 and textualelement 1201 containing calorie value (e.g., 350 CAL), active time value(e.g., 26 MIN), and standing hours value (e.g., 4 HRS). Graphicalelement 1209 includes an icon representing progress towards multipleactivity-related fitness goals (e.g., a circular icon illustratingprogress toward caloric burn, active time, and standing hours goals asthree respective concentric circular bands which progress radiallywithin the icon in proportion to progress towards the respective goals).

FIG. 12L illustrates watch user interface 1200-3 at a later time (e.g.,hour hand 1206-1 and minute hand 1206-3 indicating 1:42:30). Watch userinterface 1200-3 includes activity complication 1208-7 displaying anupdated textual element 1210 (e.g., containing calorie value of 601 CAL,active time value of 92 MIN, and standing hours value of 9 HRS) and anupdated graphical element 1209 representing illustrating elapsedprogress towards caloric burn, active time, and standing hours goals.Watch user interface 1200-3 also includes world clock complication1208-4 with an indication of time updated corresponding to the change intime between FIG. 12K and FIG. 12L.

Alternatively, as illustrated in FIGS. 12M-12N, device 600 displaysactivity complication 1208-7 in a compact form (e.g., activitycomplication 1208-7 consists of a single graphical icon positioned onclock face 1202 closer to the center of display 602 than the inner edgeof bezel 1204).

FIGS. 12M-12P illustrate embodiments of a watch user interface includinga breathe complication. FIG. 12M illustrates watch user interface 1200-4at a first time (e.g., hour hand 1206-1 and minute hand 1206-2indicating 10:42:30). Watch user interface 1200-4 includes breathecomplication 1208-8 displaying a graphical element 1209 (e.g., an iconrepresenting a corresponding meditation or mindfulness application) andtextual element 1210 containing a number of sessions performed (e.g., 2breathe sessions today).

FIG. 12N illustrates watch user interface 1200-4 at a later time (e.g.,hour hand 1206-1 and minute hand 1206-3 indicating 1:42:30). Watch userinterface 1200-4 includes breathe complication 1208-8 displayinggraphical element 1209 (e.g., an icon representing a correspondingmeditation or mindfulness application) and an updated textual element1210 (e.g., 4 breathe sessions today). Watch user interface 1200-4 alsoincludes world clock complication 1208-4 with an indication of timeupdated corresponding to the change in time between FIG. 12M and FIG.12N.

Alternatively, as illustrated in FIGS. 12O and 12P, device 600 candisplay breathe complication 1208-8 in a compact form (e.g., breathecomplication 1208-8 consists of a single graphical icon positioned onclock face 1202 closer to the center of display 602 than the inner edgeof bezel 1204).

FIGS. 12O and 12P illustrate embodiments of a watch user interfaceincluding a world clock complication. FIG. 12O illustrates watch userinterface 1200-5 at a first time (e.g., hour hand 1206-1 and minute hand1206-2 indicating 10:42:30). Watch user interface 1200-5 includes worldclock complication 1208-9 which includes graphical element 1209 (e.g.,an analog clock face with hour and minute hands) and textual element1210 including a respective location (e.g., New York), a time associatedwith the respective location (e.g., an analog clock face with hour andminute hands), and an offset (e.g., +3 hour offset to local time). Insome embodiments, the offset is used to indicate an offset to anothertime zone (e.g., GMT). Watch user interface 1200-5 also includes worldclock complication 1208-4 as described above (e.g., a compactrepresentation consisting of a graphical icon displaying respectivelocation and a time associated with the respective location (e.g.,London) positioned on clock face 1202 closer to the center of display602 than the inner edge of bezel 1204).

FIG. 12P illustrates watch user interface 1200-5 at a later time (e.g.,hour hand 1206-1 and minute hand 1206-3 indicating 1:42:30). Watch userinterface 1200-5 includes world clock complication 1208-9 displaying anupdated graphical element 1209 (e.g., an icon illustrating an analogclock face with hour and minute hands displaying 10:20) and an updatedtextual element 1210 including a location (e.g., New York), an updatedtime associated with the respective location (e.g., a textual indicationof time displaying 10:20 PM), and an offset (e.g., +3 hour offset tolocal time. Watch user interface 1200-5 also includes world clockcomplication 1208-4 with an indication of time updated to reflect thechange in time between FIG. 12O and FIG. 12P.

FIGS. 12Q and 12R illustrate embodiments of a watch user interfaceincluding a weather complication. FIG. 12Q illustrates watch userinterface 1200-6 at a first time (e.g., hour hand 1206-1 and minute hand1206-2 indicating 10:42:30). Watch user interface 1200-6 includesweather complication 1208-10 displaying graphical element 1209 (e.g.,icon illustrating sunny weather) and textual element 1210 containing adescription of current or forecasted weather (e.g., currently 79 degreesand sunny with a forecasted high temperature of 81 and a low temperatureof 62). Watch user interface 1200-6 also includes complications 1212-1(e.g., an icon illustrating sunny sky conditions from a weatherapplication) and 1212-3 (e.g., a gauge indicating a current temperatureof 79 relative to a range) as described above.

FIG. 12R illustrates watch user interface 1200-6 at a later time (e.g.,hour hand 1206-1 and minute hand 1206-2 indicating 1:42:30). Watch userinterface 1200-6 includes weather complication 1208-10 displayingupdated graphical element 1209 (e.g., icon illustrating partly sunny),updated textual element 1210 containing a description of current andforecasted weather (e.g., currently 64 degrees and partly sunny with aforecasted high temperature of 81 and a low temperature of 62), andupdated weather complications 1212-1 (e.g., icon reflecting partly sunnyweather at the second time) and 1212-3 (e.g., representing a currenttemperature of 64 relative to a range). Watch user interface 1200-6 alsoincludes world clock complication 1208-4 with an indication of timeupdated to reflect the change in time between FIG. 12Q and FIG. 12R.

FIG. 13 is a flow diagram illustrating a method for providingcontext-specific user interfaces using an electronic device inaccordance with some embodiments. Method 1300 is performed at a device(e.g., 100, 300, 500, or 600) with a display and one or more inputdevices. Some operations in method 1300 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

At block 1302, the device (e.g., 600) displays, on the display (e.g.,602), a watch user interface (e.g., 1200) including a clock face (e.g.,1202) and a user interface element (e.g., 1204) at least partiallysurrounding the clock face. In some embodiments, the clock face is acircular analog clock face (e.g., 1202). In some embodiments, the userinterface element is a portion of the area on the display surroundingthe clock face (e.g., a watch face bezel). In some embodiments, the userinterface element is a section of a ring-shaped area surrounding theclock face (e.g., clockwise from about 10 o'clock to 2 o'clock). In someembodiments, the user interface element is entirely outside the clockface (e.g., 1204 of FIGS. 12A-12B). In some embodiments, the size of theuser interface element (e.g., the angular extent of the ring-shaped areasurrounding the clock face) depends on the content associated with thefirst complication (e.g., 1204 of FIGS. 12E-12F). As used herein, abezel is a virtual rim that at least partially surrounds the area of thedisplay serving as a clock face. In some embodiments, the bezel hasmarkings associated with a particular measurement (e.g., units per hour)and is optionally rotatable. In some embodiments, the bezel is entirelyoutside (e.g., does not overlap) the clock face (e.g., 1204 of FIGS.12A-12B). Unlike a static bezel, however, in some embodiments, thevirtual bezel can be changed, as described in some of the embodimentsdescribed below.

At block 1304, the device (e.g., 600) receives, via the one or moreinput devices (e.g., 604), a request (e.g., a sequence of one or moretouch and/or rotatable input mechanism inputs) to add a respectivecomplication to a respective location on the clock face (e.g., locationof 1208-1 relative to clock face in FIGS. 12A-12C). In some embodiments,the respective location is contained entirely within the clock face(e.g., 1208-1 of FIG. 12A).

In response to receiving the request to add the respective complicationto the respective location on the clock face, the device performs theoperations of block 1306 and/or block 1308.

At block 1306, in accordance with a determination that the respectivecomplication is a first complication (e.g., 1208-5), the device (e.g.,600) displays, on the display (e.g., 602), the first complication in therespective location on the clock face and replaces at least a portion ofthe user interface element with content associated with the firstcomplication (e.g., 1208-5 of FIG. 12E). In some embodiments, the firstcomplication is associated with content related to a calendarapplication (e.g., an event or appointment description, date, time,location, etc.), weather application (e.g., sun or cloud condition, windspeed, wind direction, temperature range, humidity, etc.), exerciseapplication (e.g., standing hours, minute of activity, calories, floorsclimbed, etc.), heart rate application (e.g., current heart rate,resting heart rate, active heart rate, average heart rate, time sincelast heart rate reading, etc.), breathe application (e.g., breath count,time, etc.), or clock application (e.g., an indication of time,location, GMT offset, etc.) (e.g., FIGS. 12E-12G and 12I-12R).

Automatically presenting content in a manner that utilizes differentareas of the display based on a complication type provides the user withenhanced visual feedback by keeping the user interface less cluttered.This enables the user focus their attention on fewer visual elements andas a result, more rapidly locate relevant information throughout theinterface and interact more accurately with intended controls featureson the display. This enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user morequickly location information, and more accurately provide proper inputsand reducing user mistakes when operating/interacting with the device),which additionally reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the content associated with the first complicationincludes first content (e.g., text; data from an application of thedevice) (e.g., 1210) and the first complication includes second content(e.g., a visual label 1209) displayed in the respective location on theclock face, where the second content is associated with the firstcomplication (e.g., 1208-5 of FIGS. 12A-12G, 1208-6 of FIGS. 12I-12J,1208-7 of FIGS. 12K-12L, 1208-8 of FIGS. 12M-12N, 1208-9 of FIGS.12O-12P, and 1208-10 of FIGS. 12Q-12R).

In some embodiments, the first content represents data from anapplication and the second content represents data from the applicationthat is different than the first content (e.g., the first contentrepresents a date data from a calendar application and the secondcontent represents meeting information data from the same calendarapplication) (e.g., 1208-5, 1208-9 of FIGS. 12O-12P, 1208-10 of FIGS.12Q-12R).

In some embodiments, the first content includes textual informationassociated with the first complication (e.g., the text curves around theouter edge of the analog face) (e.g., 1210).

In some embodiments, a size of the portion of the user interface elementis based on the content associated with a first complication (e.g., inaccordance with the content being first content, the portion of the userinterface element has a first size; and in accordance with the contentbeing second content, the user interface element has a second size). Insome embodiments, the amount of the user interface element replaceddepends on the content (e.g., length of calendar event title, etc.)(e.g., 1210 of FIGS. 12E-12F). In some embodiments, the amount of theuser interface element replaced is proportional to the amount of thecontent (e.g., length, number of characters, etc.) (e.g., 1210 of FIGS.12E-12F).

Automatically adjusting the size of an element on a user interface basedon a the associated content, provides the user with enhance visualfeedback by enabling the user to focus their attention on fewer visualelements and as a result, more rapidly locate relevant informationthroughout the interface and interact more accurately with intendedcontrols features on the display. This enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user more quickly location information, and more accuratelyprovide proper inputs and reducing user mistakes whenoperating/interacting with the device), which additionally reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

At block 1308, in accordance with a determination that the respectivecomplication is a second complication (e.g., 1208-1, 1208-2, 1208-3,1208-4, 1208-6 of FIGS. 12K-12L, 1208-7 of FIGS. 12M-12N, and 1208-8 ofFIGS. 12O-12P), the device (e.g., 600) displays, on the display (e.g.,602), the second complication in the respective location on the clockface (e.g., location of 1208-1 in FIG. 12A) without replacing theportion of the user interface element with content associated with thesecond complication (e.g., FIG. 12A). In some embodiments, the secondcomplication does not include information from an associatedapplication, such as a mail, messages, or workout complication (e.g.,1208-1, 1208-6 of FIGS. 12K-12L, and 1208-8 of FIGS. 12O-12P). In someembodiments, the second complication includes content unrelated to anapplication (e.g., battery level).

In some embodiments, the second complication consists of a singlegraphical element (e.g., a visual label) (e.g., 1208-1, 1208-2, 1208-3,1208-4, 1208-6 of FIGS. 12K-12L, 1208-7 of FIGS. 12M-12N, and 1208-8 ofFIGS. 12O-12P).

Optionally, at block 1310, while displaying the content associated withthe first complication in the portion of the user interface element(e.g., FIG. 12G), the device receives an input (e.g., a tap input)corresponding to a location on the display (e.g., 1294).

In response to receiving the input corresponding to a location on thedisplay (e.g., 1294), the device optionally performs the operations ofblock 1312 and/or block 1314. At block 1312, in accordance with theinput corresponding to a location of the portion of the user interfaceelement (e.g., a portion occupied by content associated with the firstcomplication), the device launches an application associated with thefirst complication (e.g., FIGS. 12G-12H). At block 1314, in accordancewith the input corresponding to a location on the user interface elementother than the portion of the user interface element, the device forgoeslaunching an application associated with the first complication.

Selectively launching an application in an automatic fashion based onlocation of an input provides the user with more control over the deviceby helping the user quickly execute multiple commands without needing tonavigate a complex menu structure. This enables the user, interact moreaccurately with intended controls features on the display. This enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user more quickly location information,and more accurately provide proper inputs and reducing user mistakeswhen operating/interacting with the device), which additionally reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first complication (e.g., 1208-5) includes dateinformation (e.g., 1209 of FIGS. 12E-12G) (e.g., a visual labelrepresenting day of the month or week) displayed at the respectivelocation on the clock face (e.g., location of 1208-5 in FIGS. 12E-12G)and the content associated with the first complication displayed at theportion of the user interface element includes information from anappointment (e.g., 1210 of FIGS. 12E-12G) (e.g., a textual labelrepresenting a description, subject, time, location, and/or attendees,etc.). In some embodiments, the first complication (e.g., 1208-5) isassociated with a calendar application from which the date orappointment information is obtained. In some embodiments, a user inputdirected at the calendar information displayed in the respectivelocation on the clock face (e.g., 1294) launches an associated calendarapplication (e.g., FIG. 12H).

In some embodiments, the first complication (e.g., 1208-10 of FIGS.12Q-12R) includes first weather information (e.g., 1209 of FIGS.12Q-12R) (e.g., a visual label representing sun, clouds, precipitation,etc.) displayed at the respective location on the clock face (e.g., thelocation of 1208-10 in FIGS. 12Q-12R) and the content associated withthe first complication displayed at the portion of the user interfaceelement includes second weather information different than the firstweather information (e.g., 1210 of FIGS. 12Q-12R) (e.g., a textual labelrepresenting sun or cloud condition, wind speed, wind direction,temperature range, humidity, and/or location, etc.). In someembodiments, the first complication is associated with a weatherapplication from which first or second weather information is obtained.In some embodiments, a user input directed at the first weatherinformation displayed in the respective location on the clock facelaunches an associated weather application.

In some embodiments, the first complication (e.g., 1208-7 of FIGS.12K-12L) includes first exercise information (e.g., 1209 of FIGS.12K-12L) displayed at the respective location on the clock face (e.g.,the location of 1208-10 in FIGS. 12K-12L) and the content associatedwith the first complication displayed at the portion of the userinterface element includes second exercise information different thanthe first exercise information (e.g., 1210 of FIGS. 12Q-12R) (e.g., atextual label representing steps taken, floors climbed, hours stood,calories burned, and/or time active, etc.). In some embodiments, firstexercise information includes a visual label (e.g., 1209 of FIGS.12Q-12R) representing one or more fitness goals and progress toward them(e.g., steps taken, floors climbed, hours stood, calories burned, timeactive, etc.). In some embodiments, the first complication is associatedwith an exercise application from which first or second exerciseinformation is obtained. In some embodiments, a user input directed atthe first exercise information displayed in the respective location onthe clock face launches an associated exercise application.

In some embodiments, the first complication (e.g., 1208-6 of FIGS.12I-12J) includes an affordance displayed at the respective location onthe clock face (e.g., the location of 1208-6 in FIGS. 12I-12J) (e.g., aheart-shaped visual label) and the content associated with the firstcomplication displayed at the portion of the user interface elementincludes heart rate information (e.g., 1210 of FIGS. 12I-12J) (e.g., atextual label representing current heart rate, resting heart rate,active heart rate, average heart rate, time since last heart ratereading, etc.). In some embodiments, the first complication isassociated with a heart rate application from which heart rateinformation is obtained. In some embodiments, a user input directed atthe affordance displayed in the respective location on the clock facelaunches an associated heart rate application.

In some embodiments, the first complication (e.g., 1208-7 of FIGS.12M-12N) includes an affordance displayed at the respective location onthe clock face (e.g., the location of 1208-7 in FIGS. 12M-12N) and thecontent associated with the first complication is displayed at theportion of the user interface includes meditation or mindfulnessinformation (e.g., 1210 in FIGS. 12M-12N). In some embodiments, theaffordance is a visual label (e.g., 1209 of FIGS. 12M-12N) representinga meditation or mindfulness application (e.g., a breathe application).In some embodiments, meditation or mindfulness information includes atextual label (e.g., 1210 of FIGS. 12M-12N) representing breath count,session count, time, etc. In some embodiments, the first complication isassociated with a meditation or mindfulness application from whichmeditation or mindfulness information is obtained. In some embodiments,a user input directed at the affordance displayed in the respectivelocation on the clock face launches an associated meditation ormindfulness application.

In some embodiments, the first complication (e.g., 1208-9 of FIGS.12O-12P) includes first time information (e.g., 1209 of FIGS. 12O-12P)(e.g., an analog clock including an hour hand and a minute hand)displayed at the respective location on the clock face (e.g., thelocation of 1208-9 in FIGS. 12O-12P) and the content associated with thefirst complication displayed at the portion of the user interfaceelement includes second time information different than the first timeinformation (e.g., 1210 of FIGS. 12O-12P) (e.g., digital indication oftime, location, GMT offset, and/or etc.). In some embodiments, the firstcomplication is associated with a clock application from which first andsecond time information is obtained. In some embodiments, a user inputdirected at the first time information displayed in the respectivelocation on the clock face launches an associated meditation clock ormindfulness application.

Note that details of the processes described above with respect tomethod 1300 (e.g., FIG. 13) are also applicable in an analogous mannerto the methods described above. For example, method 1300 optionallyincludes one or more of the characteristics of the various methodsdescribed above with reference to method 1100. For example, watch userinterface 1200 of FIG. 12A can be configured to display threecomplications, including at least two metrics (e.g., complications1008-1, 1008-2, and 1008-3 of FIG. 10A), in a manner analogous totechniques described with reference to method 1100. For brevity, thesedetails are not repeated below.

FIGS. 14A-14AE illustrate exemplary watch user interfaces, in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the methods in FIGS.15A-15C.

FIG. 14A illustrates device 600 as described above. As illustrated inFIG. 14A, device 600 displays watch user interface 1400 on display 602.Watch user interface 1400 includes clock face 1402 surrounded by bezel1404. Clock face 1402 includes an indication of time having hour hand1406-1, minute hand 1406-2, and second hand 1406-3. Bezel 1404 includeshour markings 1405 (e.g., evenly spaced graphical markings that providea visual reference to assist a user of device 600 in quickly determininga time displayed on clock face 1402). Watch user interface 1400 alsoincludes date complication 1408-1, music complication 1208-2, timercomplication 1208-3, and world clock complication 1208-4. Datecomplication 1408-1 displays data from an associated date or calendarapplication (e.g., day of the week and day of the month). Musiccomplication 1208-2, timer complication 1208-3, world clock complication1208-4, as described above, includes metrics related to data fromrespective applications. In FIG. 14A, complications 1208-1, 1208-2,1208-3, and 1208-4 occupy respective locations in the upper, right,lower, and left regions of the clock face 1402. Watch user interface1500 also includes corner complications 1212-1, 1212-2, 1212-3, and1212-4 as described above.

As illustrated in FIG. 14A, device 600 receives (e.g., detects) userinput 1490 (e.g., a long press on display 602) corresponding to arequest to edit watch user interface 1400. In response to user input1490, device 600 enters an edit mode (e.g., watch face edit mode orcomplication edit mode). In FIG. 14B, device 600 indicates edit mode byvisually distinguishing date complication 1408-1 for editing (e.g., bydisplaying box 1414 around date complication 1408-1 and label 1416identifying the associated application). In some embodiments, device 600visually distinguishes the complication selected for editing (e.g., datecomplication 1408-1) by varying one or more visual properties (e.g.,brightness, opacity, color, contrast, hue, saturation, etc.) of watchuser interface 1400, or portions thereof. In some embodiments, while inedit mode, the complication selected for editing is displayed with afirst visual property (e.g., in color or a plurality of colors otherthan greyscale) and one or more other complications (e.g., all othercomplications) are displayed with a second visual property (e.g., ingreyscale or in a single color different from the plurality of colorsthat the complication would otherwise be displayed in when the device isnot in the edit mode) even though, in some embodiments, some or all ofthe other complications are displayed in one or more colors in the watchface when the watch face is displayed while the device is not in theedit mode. For example, complication 1408-1 is displayed in color andcomplications 1208-2, 1208-3, and 1208-4 are displayed in greyscale. Insome embodiments, while in edit mode, a visual property of one or moreof the unselected complications is changed (e.g., a brightness oropacity of one or more of the unselected complications is reduced todistinguish the unselected complications from the selected complication)instead of, or in addition to, the change to the visual property of theone or more selected complications. In some embodiments, the visualdistinguishing of the selected complication is instead of or in additionto an alternative selection indicator such as a selection ring around atleast a portion of the selected complication. While in edit mode, device600 also displays complication menu bar 1418 with complication positionindicator 1420, which indicates the position of the currently displayedcomplication within a menu of complications available for selection. Insome embodiments, user input 1490 includes a contact having acharacteristic intensity and device 600 enters the edit mode inaccordance with a determination that the characteristic intensityexceeds a predetermined threshold intensity.

As illustrated in FIG. 14C, device 600 receives (e.g., detects) userinput 1492, which includes rotation of rotatable input mechanism 604. Insome embodiments, user input 1492 is received at another device thatcommunicates with device 600 (e.g., via a companion applicationassociated with device 600 running on the other device). In response toreceiving user input 1492, device 600 displays a representation oftachymeter complication 1408-2 to add to watch user interface 1400 inplace of date complication 1408-1. In FIG. 14D, device 600 updatescomplication position indicator 1420 to indicate that tachymetercomplication 1408-2 is located near the bottom of the complication menu(e.g., because the complications are in alphabetical order and “t” isnear the end of the alphabet). As illustrated in FIG. 14D, therepresentation of tachymeter complication 1408-5 includes an indicationof the type of information tachymeter complication 1408-5 will displayon watch user interface 1400 upon exiting the edit mode (e.g., genericunits).

In some embodiments, while in edit mode, device 600 receives (e.g.,detects) one or more inputs (e.g., a tap on display 602 or a press ofrotatable input mechanism 604) corresponding to a request to exit editmode. In response to exiting edit mode, device 600 adds tachymetercomplication 1408-2 to watch user interface 1400, replacing datecomplication 1408-1 in the upper region of clock face 1402. Asillustrated in FIG. 14E, tachymeter complication 1408-2 displays a unitsdisplay 1412 positioned on clock face 1402 closer to the center ofdisplay 602 than the inner edge of bezel 1404, without overlapping withthe area occupied by bezel 1204.

As illustrated in FIG. 14F, device 600 receives (e.g., detects) userinput 1494 (e.g., a tap on display 602 in the area occupied by unitsdisplay 1412). In some embodiments, user input 1494 is detected bydevice 600 at a location on display 1402 corresponding to bezel 1404. Inresponse to user input 1494, device 600 updates watch user interface1400. In FIG. 14G, watch user interface 1400 includes bezel 1404, wherehour markings 1405 have been replaced by units scale 1422 (e.g., 60units per hour scale) and tachymeter hand 1424 has been added. In someembodiments, hour markings 1405 are replaced by units scale 1422 inresponse to user input 1492 (selection rotation) and only tachymeterhand 1424 is added to watch user interface 1400 in response to userinput 1494. In some embodiments, in response to user input 1492(selection rotation), hour markings 1405 are replaced by units scale1422 and tachymeter hand 1424 is added to watch user interface 1400.

Automatically updating the interface in response in response to aspecific user interaction (e.g., after exiting edit mode), provides theuser with enhanced visual feedback by keeping the user interface lesscluttered during the selection. This enables the user focus theirattention on fewer visual elements and as a result, more rapidly locaterelevant information throughout the interface and interact moreaccurately with intended controls features on the display. This enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user more quickly location information,and more accurately provide proper inputs and reducing user mistakeswhen operating/interacting with the device), which additionally reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

As illustrated in FIG. 14H, device 600 receives (e.g., detects) userinput 1496 (e.g., a tap display corresponding to tachymeter hand 1424 orbezel 1404 with units scale 1422). In response to receiving user input1496, device 600 updates watch user interface 1400 (e.g., rotation oftachymeter hand 1424 is started and units display 1412 updatescorresponding to the location of tachymeter hand 1424 relative unitsscale 1422). In FIG. 14I, tachymeter hand 1424 has progressed to alocation on bezel 1404 corresponding to 144 units, units display 1412reflects the position of tachymeter hand 1424 (e.g., 144 units), andsecond hand 1406-3 indicates 20 seconds have elapsed.

In some embodiments, while the tachymeter hand 1424 is progressing(e.g., rotating), device 600 receives a subsequent user input (e.g., atap on the user display). In response, the tachymeter hand 1424 andunits display 1412 stop updating (e.g., tachymeter hand stops rotatingand units display value reflects the position of the tachymeter handrelative to units scale 1422). In some embodiments, the subsequent userinput (e.g., a tap or long-press on the user display) resets thetachymeter complication (e.g., bezel 1404, tachymeter hand 1424, andunits display 1412 return their respective states illustrated in FIG.14G).

As illustrated in FIG. 14J, prior to user input 1496 (e.g., beforestarting the rotation of tachymeter hand 1424), device 600 receives(e.g., detects) user input 1498-1, which includes rotation of rotatableinput mechanism 604. In response to receiving user input 1498-1, device600 updates units scale 1422 on bezel 1404. FIG. 14K includes updatedunits scale 1422 (e.g., indicating selection of a 30 units per hourscale for tachymeter functions).

Turning now to FIG. 14M, the process of updating watch user interface1400 with diver complication 1408-3 is illustrated (e.g., afterselection of a diver complication from edit mode, device 600 displays arepresentation of diver complication 1408-3 to add to watch userinterface 1400, and upon exiting edit mode, device 600 adds divercomplication 1408-3 to watch user interface 1400, replacing thecomplication in the upper region of clock face 1402). As illustrated inFIG. 14M, diver complication 1408-3 includes minutes display 1426positioned on clock face 1402 closer to the center of display 602 thanthe inner edge of bezel 1404, without overlapping with the area occupiedby bezel 1204.

In FIG. 14M device 600 receives (e.g., detects) user input 1491 (e.g., atap on display 602 in the area occupied by minutes display 1426). Insome embodiments, user input 1491 is detected by device 600 at alocation on display 1402 corresponding to bezel 1404. In response touser input 1491, device 600 updates watch user interface 1400. In FIG.14N, updated watch user interface 1400 includes bezel 1404 where hourmarkings 1405 have been replaced by diver scale 1430 (e.g., numeralsaround the bezel corresponding to minutes) and bezel marker 1428 hasbeen added bezel 1404 (e.g., at top of the bezel).

As illustrated in FIGS. 14N-14P, device 600 receives (e.g., detects)user input 1493, which includes rotation of rotatable input mechanism604. In response to user input 1493, device 600 updates watch userinterface 1400 by updating the position (e.g., rotating) bezel 1404. Asillustrated by the progression of bezel marker 1428 to a positionaligned with minute hand 1206-2 in FIG. 14P, bezel 1404 moves clockwisein response to user input 1493. In other embodiments, bezel 1404progresses counter-clockwise in response to user input 1493.

FIG. 14Q illustrates watch user interface 1400 sometime after thecompletion of user input 1493. Minutes display 1426 indicates the offsetbetween bezel 1404 and minute hand 1206-2 (e.g., that 18 minutes haveelapsed since the bezel was aligned with the minute hand) andindications of time have been updated (e.g. minute hand 1206-2 and worldclock complication 1208-4 are updated corresponding to the change intime between FIG. 14P and FIG. 14Q).

Turning now to FIG. 14R, a process is described for updating watch userinterface 1400 with GMT complication 1408-4 (e.g., after selection of aGMT complication from edit mode, device 600 displays a representation ofGMT complication 1408-4 to add to watch user interface 1400; and uponexiting edit mode, device 600 adds GMT complication 1408-4 to watch userinterface 1400, replacing the complication in the upper region of clockface 1402). As illustrated in FIG. 14R, GMT complication 1408-4 includesoffset display 1432 (e.g., representing a time-zone for display by GMThand, relative to GMT time) positioned on clock face 1402 closer to thecenter of display 602 than the inner edge of bezel 1404 (e.g., withoutoverlapping with the area occupied by bezel 1204), GMT scale 1436 onbezel 1404 (e.g., 24-hour scale), and GMT hand 1434 (e.g., handpositioned relative to GMT scale 1436 to indicate time in a time-zonebased to the offset displayed).

As illustrated in FIGS. 14R-14T, device 600 receives (e.g., detects)user input 1495, which includes rotation of rotatable input mechanism604. In response to user input 1495, device 600 updates watch userinterface 1400 by incrementing hour offset displayed on offset display1432 (e.g. +0 HRS to +1 HRS to +3 HRs), and updating the position of GMThand 1434 relative to GMT scale 1436 (e.g., GMT hand 1434 rotates aroundbezel to reflect change in offset).

Similar to the process described in reference to FIGS. 14A-14D, a usercan request to add a compact complication consisting of a singlegraphical element (e.g., a complication without associated bezel contentsuch as workout complication 1208-1) in place of GMT complication 1408-4by selecting complication 1408-4 (e.g., with a tap) in edit mode andmoving rotatable input mechanism 604 to select the new complication1208-1. FIG. 14U illustrates watch user interface 1400 after exitingedit mode (e.g., GMT hand 1434 is removed, offset display 1432 isreplace by workout complication 1208-1, and GMT scale 1436 is replacedby hour markings 1405 on bezel 1404).

Turning now to FIGS. 14V-14AE, various functions associated withrotatable input mechanism 604 are described.

In FIG. 14V, device 600 displays mail application interface 1400-2 ondisplay 602. Mail application interface 1400-2 includes applicationheader 1438 (e.g., application label and indication of time), andcontent display area 1440. Content display area 1440 includes subjectline 1442, and message content 1444. As illustrated in FIGS. 14V and14W, device 600 receives (e.g., detects) user input 1497, which includesrotation of rotatable input mechanism 604. In response to user input1497, device 600 updates mail application interface 1400-2 bytranslating subject line 1442 and message content 1444 (e.g., scrolling)upward from a first position on display 602 to a second position ondisplay 602. As illustrated in FIG. 14W, subject line 1442 and/ormessage content 1444 is scrolled to a position outside of contentdisplay area 1440 and, as a result, are not displayed on display 602. Insome embodiments, the direction of user input 1497 corresponds to thedirection of translation of message content 1444 on display 602.

In FIG. 14X, device 600 displays application selection interface 1400-3on display 602. Application selection interface 1400-3 includes avertical list of application icons including activity icon 1446-1, alarmicon 1446-2, breathe icon 1446-3, and camera icon 1446-3 (collectively,“application icons 1446”). As illustrated in FIGS. 14X and 14V, device600 receives (e.g., detects) user input 1497, which includes rotation ofrotatable input mechanism 604. In response to user input 1497, device600 updates application selection interface 1400-3 by translatingapplication icons 1446 (e.g., scrolling) upward from a first position ondisplay 602 to a second position on display 602. As illustrated in FIG.14W, one or more application icons 1446 scroll to a position outside ofdisplay 602 and as a result are not displayed on display 602. In someembodiments, the direction of user input corresponds to the direction oftranslation of application icons 1446 on display 602.

In FIG. 14Z, display 602 of device 600 is off (e.g., screen is notdisplaying content or emitting light). As illustrated in FIG. 14Z,device 600 receives (e.g., detects) user input 1497, which includesrotation of rotatable input mechanism 604. In FIG. 14AA, in response touser input 1497, device 600 turns on display 602 (e.g., screen displayswatch user interface 1400-4 including a clock face containing hourmarkings, indication of time, and date display).

FIG. 14AB illustrates device 600 displaying watch user interface 1400-5including clock face 1402, indication of time (hour hand 1406-1, minutehand 1406-2, and second hand 1406-3) (e.g., indicating 10:40:35), andnext appointment indicator 1452 (e.g., representing a user's nextappointment relative to the displayed time on clock face 1402 is a 12 PMlunch). As illustrated in FIG. 14AB, device 600 receives (e.g., detects)user input 1497-1, which includes rotation of rotatable input mechanism604. In response to receiving user input 1497-1, device 600 updateswatch user interface 1400-5 (e.g., advancing the displayed indication oftime proportional to input 1497-1). FIG. 14AC illustrates updated watchuser interface 1400-5. Watch user interface 1400-5 includes time offsetlabel 1454 (e.g., +2:21 Time Travel), indication of time (hour hand1406-1, minute hand 1406-2, and second hand 1406-3) (e.g., indicating1:55), and next appointment indicator 1452 (e.g., 3 PM—Meeting).

In FIG. 14AD, device 600 displays application selection interface 1400-6on display 602. Application selection interface 1400-6 includes acollection of application icons including alarm icon 1456-1, weathericon 1456-2, messages icon 1456-3, clock icon 1456-4, activity icon1456-5, to-do icon 1456-6, heart rate icon 1456-7, and calendar icon1456-8 (collectively, “application icons 1456”). As illustrated in FIG.14AD, device 600 receives (e.g., detects) user input 1497-1, whichincludes rotation of rotatable input mechanism 604. In response to userinput 1497-1, device 600 updates application selection interface 1400-6by launching the application corresponding to the application icondisplayed closest to the center of display 602 (e.g., alarm icon). FIG.14AE illustrates alarm application interface 1400-7 associated with thealarm application displayed on display 602. Alarm application interface1400-7 includes an application label 1460 (e.g., alarms), indication oftime (e.g. 10:09), alarm display 1458-1 (e.g. time, label, and on/offswitch) and alarm generation affordance 1458-2.

FIGS. 15A-15C are a flow diagram illustrating a method for providingcontext-specific user interfaces using an electronic device inaccordance with some embodiments. Method 1500 is performed at a device(e.g., 100, 300, 500, or 600) with a display and one or more inputdevices. Some operations of method 1500 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

At block 1502, the device (e.g., 600) displays, on the display (e.g.,602), a watch user interface (e.g., 1400) including a clock face (e.g.,1402), a user interface element at least partially surrounding the clockface (e.g., 1404) (e.g., a watch face bezel) and a complication (e.g.,1408-1). In some embodiments, a complication, refers to any clock facefeature other than those used to indicate the hours and minutes of atime (e.g., clock hands or hour/minute indications). In someembodiments, a complication includes an affordance that when selectedlaunches a corresponding application (e.g., 1408-1, 1208-2, 1208-3,1208-4). In some embodiments, complications provide data obtained froman application (e.g., 1408-1, 1208-2, 1208-3, 1208-4). In someembodiments, a complication is displayed at a fixed, predefined locationon the display (e.g., 1408-1, 1208-2, 1208-3, and 1208-4). In someembodiments, the complication is displayed within the clock face (e.g.,1408-1, 1208-2, 1208-3, 1208-4) (e.g., completely within the clockface). In some embodiments, the complication is displayed between theuser interface element and an edge of the display (e.g., 1212-1, 1212-2,1212-3, and 1212-4).

Presenting information in a manner that conforms to space available onthe clock face provides the user with enhanced visual feedback bykeeping the user interface less cluttered. This enables the user focustheir attention on fewer visual elements and as a result, more rapidlylocate relevant information throughout the interface and interact moreaccurately with intended controls features on the display. This enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user more quickly location information,and more accurately provide proper inputs and reducing user mistakeswhen operating/interacting with the device), which additionally reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

At block 1504, while displaying the watch user interface (e.g., 1400),the device detects, via one or more input devices (e.g., 604), an inputdirected to the user interface element (e.g., 1490, 1492, 1494, 1496).In some embodiments, the input directed to the user interface elementincludes a tap gesture at a location on the display corresponding to theuser interface element (e.g., 1494, 1496).

At block 1506, in response to detecting the input directed to the userinterface element, the device updates, on the display (e.g., 602), anappearance (e.g., 1405) of the user interface element (e.g., 1404) basedon the input while maintaining display of the clock face (e.g., 1402)and the complication (e.g., 1408-2) on the display.

In some embodiments, in accordance with a determination that thecomplication is a complication of a first type (e.g., 1408-2, 1408-3,1408-4), the user interface element includes a first visualcharacteristic (e.g., 1422, 1430) (e.g., a numeric scale) correspondingto first complication and in accordance with a determination that thecomplication is not a complication of the first type (e.g., 1408-1), theuser interface element includes a second visual characteristic (e.g.,1405) (e.g., minute or hour tick marks) different than the first visualcharacteristic, where the second visual characteristic is independentfrom the complication (e.g., hour markers are independent from batterylevel, mail, messages, etc.). In some embodiments, the firstcomplication is associated with content related to a tachymeter (e.g.FIGS. 14E-14I), an offset (e.g., 1426) (e.g., diver bezel), or GMT time(e.g., FIGS. 14R-14T)). In some embodiments, the complication (e.g., acomplication of a second type) is associated with a battery level orother types of application, such as calendar, mail, messages, etc.).

Automatically updating the appearance of a user interface element basedon the type of complication provides the user with enhanced visualfeedback by keeping the user interface less cluttered and onlydisplaying relevant features. This enables the user focus theirattention on fewer visual elements and as a result, more rapidly locaterelevant information throughout the interface and interact moreaccurately with intended controls features on the display. This enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user more quickly location information,and more accurately provide proper inputs and reducing user mistakeswhen operating/interacting with the device), which additionally reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the user interface element (e.g., 1404) includes ascale indicating generic units (which can represent, e.g., miles, km,parts) per a predetermined unit of time (e.g., second, hour, day) andthe clock face (e.g., 1402) includes a rotating hand (e.g., 1424)indicating a position on the scale (e.g., 1422) and the complication(e.g., 1408-2) includes units information (e.g., 1412) corresponding tothe position on the scale (e.g., 1422) indicated by the rotating hand(e.g., 1424). In some embodiments, units information represents theamount of units per the predetermined unit of time based on an elapsedtime.

Optionally, at block 1508, the device detects a first input (e.g., 1496)corresponding to selection of the complication and performs theoperations of blocks 1510, 1512, and 1514. At block 1510, in response todetecting the first input, the device starts the rotating hand (e.g.,1424) and updates the units information (e.g., 1412). At block 1512, thedevice detects a second input corresponding to selection of thecomplication, the second input detected after the first input. At block1514, in response to detecting the second input, the device stops orresets the rotating hand (e.g., 1424) and the units information (e.g.,1412). In some embodiments, starting the rotating hand (e.g., 1424) andupdating the units displayed in the complication occurs withoutnavigating to a corresponding application. In some embodiments, stoppingor resetting the rotating hand and the units displayed in thecomplication occurs without navigating to a corresponding application.

In some embodiments, the complication is a first complication associatedwith content related to a tachymeter, an offset (e.g., diver bezel), orGMT time (e.g., 1408-2, 1408-3, 1408-4) and the device performs theoperations of blocks 1516 and 1518. At block 1516, the device receives,via the one or more input devices (e.g., 604), a request (e.g., 1490,1492) to change the first complication (e.g., 1408-1) to a secondcomplication (e.g., 1408-2). In some embodiments, a first complication(e.g., a complication of a first type). In some embodiments, a secondcomplication (e.g., a complication of a first type) is associated withcontent related to a tachymeter, an offset (e.g., diver bezel), or GMTtime. In some embodiments, a second complication (e.g., a complicationof a second type) is associated with a battery level or other types ofapplication (e.g., calendar, mail, messages, etc.). At block 1518, inresponse to detecting the request to change the first complication to asecond complication, the device replaces the first complication with thesecond complication and updates, on the display, the appearance of theuser interface element based on the second complication (e.g., FIG.14G).

In some embodiments, the complication is a first complication and thedevice performs the operations of block 1520 and 1522. In someembodiments, a first complication does not have a functionality tied tothe user interface element (e.g., 1408-1, 1208-1). At block 1520, thedevice (e.g., 600) receives, via the one or more input devices (e.g.,604), a request to change the first complication to a secondcomplication different than the first complication. In some embodiments,a second complication is a type of complication that does not have afunctionality tied to the user interface element (e.g., 1408-1, 1208-1).In some embodiments, a second complication (e.g., a complication of asecond type) is associated with a battery level or other types ofapplication (e.g., calendar, mail, messages, etc.). At block 1522, inresponse to detecting the request to change the first complication tothe second complication, the device replaces the first complication withthe second complication and maintains the appearance of the userinterface element. In some embodiments, a first complication (e.g., acomplication of a first type) is associated with a battery level orother types of application, such as calendar, mail, messages, etc.).

In some embodiments, the complication is a first complication positionedat a first location of the watch user interface (e.g., 1408-2), thewatch user interface includes a second complication different than thefirst complication positioned at a second location of the watch userinterface different than the first location (e.g., 1208-2, 1208-3,1208-4) and the device performs the operations of blocks 1524 and 1526.At block 1524, the device detects a first input corresponding toselection of the second complication and at block 1526, in response todetecting the first input, the device launches an applicationcorresponding to the second complication.

In some embodiments, the one or more input devices includes a rotatableinput mechanism (e.g., a mechanism that can rotate relative to ahousing/body of the electronic device) and input directed to the userinterface element includes a rotation of the rotatable input mechanism(e.g., 1492, 1493-1, 1493-2, 1495-1, 1495-2, 1498-1, 1498-2). In someembodiments, rotation of the rotatable input mechanism (e.g., 604) isabout an axis parallel to the display (e.g., 602).

Optionally, at block 1528, the device, while displaying the clock faceon the display (e.g., 602), detects a rotation of the rotatable inputmechanism (e.g., 604) and in response to detecting the rotation of therotatable input mechanism, adjusts the complication (e.g., FIGS.14J-14K, 14N-140, 14R-14T). In some embodiments, rotation of therotatable input mechanism is about an axis parallel to the display(e.g., 602). In some embodiments, adjusting the complication includeschanging the complication from a first complication to a secondcomplication (e.g., FIGS. 14A-14F). In some embodiments, rotating therotatable input mechanism updates the appearance of the user interfaceelement in accordance with the adjustment of the complication (e.g.,FIGS. 14N-140) (e.g., for a watch face with a diver bezel and acorresponding complication, the user interface element is rotatedrelative to the clock face and the corresponding complication isadjusted to reflect the offset between an indication on the userinterface element and the minute hand). In some embodiments, rotatingthe rotatable input mechanism (e.g., 604) updates the appearance of theclock face (e.g., 1402) in accordance with the adjustment of thecomplication (e.g., for a watch face with a GMT bezel and acorresponding complication, the GMT hand is rotated in accordance withan adjustment in an offset indicated by the complication (e.g., FIGS.14R-14T).

Updating the positioning of multiple graphical elements on a display inresponse to analogous rotational input at a user input provides the userwith feedback about how interactions with the device will change theconfiguration of user interface, this enables the user to choose theirnext input more efficiently. Providing improved visual feedback to theuser enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

Optionally, at block 1530, the device displays, on the display (e.g.,602), content different than the watch user interface (e.g., 1400-2,1400-3) and while displaying the content different than the watch userinterface, the device detects a rotation of the rotatable inputmechanism (e.g., 604) and in response detecting the rotation of therotatable input mechanism, the device scrolls the content on the display(e.g., FIGS. 14V-14W, 14X-14Y). In some embodiments, rotation of therotatable input mechanism is about an axis parallel to the display.

Optionally, at block 1532, the device displays, on the display, aplurality of application affordances (e.g., 1456-1, 1456-2, 1456-3,1456-4, 1456-5, 1456-6, 1456-7) (e.g., in a springboard/home screen userinterface) and while displaying the plurality of applicationaffordances, the device detects a rotation of the rotatable inputmechanism (e.g., 604) and in response to detecting the rotation of therotatable input mechanism, the devices launches an application (e.g.,1400-7) associated with a first application affordance (e.g., anaffordance located at the center of the display) of the plurality ofapplication affordances. In some embodiments, rotation of the rotatableinput mechanism is about an axis parallel to the display. In someembodiments, in response to detecting the rotation, the electronicdevice initially zooms into a portion of the displayed plurality ofapplication affordances and, upon further rotation, launches anapplication that corresponds to the centermost affordance.

Optionally, at block 1534, while the display is off (e.g., 602 of FIG.14Z), the device detects a rotation of the rotatable input mechanism(e.g., 604) and in response to detecting the rotation of the rotatableinput mechanism while the display is off, the device turns on thedisplay (e.g., 602 of FIG. 14AA) (e.g., gradually turning on the displayas the rotation of the rotatable input mechanism progresses optionallybased on a speed or amount of rotation of the rotatable inputmechanism). In some embodiments, rotation of the rotatable inputmechanism is about an axis parallel to the display. Dynamicallycontrolling the state of the display in response to user input allowsthe user to operate the device in manner where screen is off for periodsof time thereby using less energy. This enables the device to conservepower and improves battery life.

In some embodiments, the user interface element includes a rotatablescale (e.g., 1430) and the complication includes a value (e.g., 1426)indicating the position of a hand on the clock face relative to therotatable scale (e.g., the minutes offset between a marker (e.g., a redtriangle) indicating the beginning of the scale and the position of theminute hand).

In some embodiments, the one or more input devices includes a rotatableinput mechanism (e.g., a mechanism that can rotate relative to ahousing/body of the electronic device) the device, while displaying theclock face on the display (e.g., 602), detects a rotation of therotatable input mechanism (e.g., 604) and in response to detecting therotation of the rotatable input mechanism, the device rotates the scale(e.g., 1430) of the user interface element on the display (e.g., toalign a starting marker (e.g., 1428) (e.g., red arrow) with the minutehand). In some embodiments, rotation of the rotatable input mechanism isabout an axis parallel to the display.

Automatically updating a visual characteristic, such as the position ofone or more graphical elements in response to an input, provides theuser with more control over the device by helping the user quicklyconfigure display elements into a variety configurations without therequiring individual interactions with each element (e.g., firstselecting an element, then relocating the element to another location onthe display, individually adjusting nature of information displayed andrepeating the steps for other elements are condensed into feweroperations that require user input). Reducing the number of inputs needto perform equivalent operations, enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the complication includes an hours offset (e.g.,1432) from a predetermined time (e.g., local time or Greenwich MeanTime) and the user interface element (e.g., 1404) includes a time scale(e.g., 1430) (e.g., 24 hours) and the clock face (e.g., 1404) includes ahand (e.g., 1434) (e.g., the hand is a “GMT hand”) that indicates aposition on the time scale corresponding to the offset, wherein the handrotates at a rate corresponding to the time scale. In some embodiments,the one or more input devices includes a rotatable input mechanism(e.g., a mechanism that can rotate relative to a housing/body of theelectronic device) and while displaying the clock face on the display,the device detects a rotation of the rotatable input mechanism and inresponse to detecting the rotation of the rotatable input mechanism, thedevice changes the hours offset displayed at the complication and aposition of the hand in accordance with the change in the hours offset(e.g., FIGS. 14R-14S). In some embodiments, the hand is a “GMT hand” ora hand representing any reference time zone. In some embodiments,rotation of the rotatable input mechanism is about an axis parallel tothe display.

Automatically updating a visual characteristic, such as the position ofone or more graphical elements in response to an input, provides theuser with more control over the device by helping the user quicklyconfigure display elements into a variety configurations without therequiring individual interactions with each element (e.g., firstselecting an element, then relocating the element to another location onthe display, individually adjusting nature of information displayed andrepeating the steps for other elements are condensed into feweroperations that require user input). Reducing the number of inputs needto perform equivalent operations, enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Note that details of the processes described above with respect tomethod 1500 (e.g., FIGS. 15A-15C) are also applicable in an analogousmanner to the methods described above. For example, method 1500optionally includes one or more of the characteristics of the variousmethods described above with reference to method 1100. For example,watch user interface 1400 of FIG. 14A can be configured to display threecomplications, including at least two metrics (e.g., complications1008-1, 1008-2, and 1008-3 of FIG. 10A), in a manner analogous totechniques described with reference to method 1100. For brevity, thesedetails are not repeated below.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to provideinsights into a user's general wellness. The present disclosurecontemplates that in some instances, this gathered data may includepersonal information data that uniquely identifies or can be used tocontact or locate a specific person. Such personal information data caninclude demographic data, location-based data, telephone numbers, emailaddresses, twitter IDs, home addresses, data or records relating to auser's health or level of fitness (e.g., vital signs measurements,medication information, exercise information), date of birth, or anyother identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toprovide positive feedback to individuals using technology to pursuewellness goals. Accordingly, use of such personal information dataenables users to pursue individually tailored fitness goals andotherwise, modify their behavior to improve a user's general wellnessand health. Further, other uses for personal information data thatbenefit the user are also contemplated by the present disclosure. Forinstance, personal information data may be used to deliver targetedcontent that is of greater interest to the user.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence, different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, health andfitness applications, the present technology can be configured to allowusers to select to “opt in” or “opt out” of participation in thecollection of personal information data during registration for servicesor anytime thereafter. In another example, users can select not toprovide data or records relating to a user's health or level of fitness(e.g., vital signs measurements, medication information, exerciseinformation). In yet another example, users can select to limit thelength of time health and fitness data is maintained or entirelyprohibit the development of a baseline health or fitness profile. Inaddition to providing “opt in” and “opt out” options, the presentdisclosure contemplates providing notifications relating to the accessor use of personal information. For instance, a user may be notifiedupon downloading an app that their personal information data will beaccessed and then reminded again just before personal information datais accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, fitness goalscan be selected and delivered to users by inferring exerciserequirements based on non-personal information data or a bare minimumamount of personal information, such as non-personal informationavailable to the health and fitness applications, or publicly availableinformation.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. An electronic device, comprising: a display,wherein the display has one or more corners; one or more processors; andmemory storing one or more programs configured to be executed by the oneor more processors, the one or more programs including instructions for:displaying a watch user interface on the display, the watch userinterface including: an analog clock face area, the analog clock facearea including an area of the display in which an hour hand and a minutehand rotate; a first complication, wherein the first complication islocated outside of the analog clock face area and is in a first cornerof the one or more corners of the display, wherein the firstcomplication includes at least: a first metric related to data from afirst application; a second metric related to data from the firstapplication; a status bar that tracks an outer edge of the analog clockface area; and a value located between the status bar and the firstcorner of the display; a second complication that includes at least athird metric related to data from a second application and a fourthmetric related to data from the second application; and a thirdcomplication that includes at least a fifth metric related to data froma third application and a sixth metric related to data from the thirdapplication; detecting a sequence of one or more inputs that correspondsto a request to add a fourth complication to the watch user interface,wherein the fourth complication includes at least a seventh metricrelated to data from a fourth application and an eighth metric relatedto data from the fourth application; and in response to detecting thesequence of one or more inputs: in accordance with a determination thatthe sequence of one or more inputs corresponds to a request to replacethe first complication, replacing the first complication outside of theanalog clock face area with the fourth complication; in accordance witha determination that the sequence of one or more inputs corresponds to arequest to replace the second complication, replacing the secondcomplication with the fourth complication; and in accordance with adetermination that the sequence of one or more inputs corresponds to arequest to replace the third complication, replacing the thirdcomplication with the fourth complication.
 2. The electronic device ofclaim 1, the one or more programs further including instructions for: inresponse to detecting the sequence of one or more inputs: in accordancewith a determination that the sequence of one or more inputs correspondsto a request to replace the first complication, maintaining the secondcomplication and the third complication; in accordance with adetermination that the sequence of one or more inputs corresponds to arequest to replace the second complication, maintaining the firstcomplication and the third complication; and in accordance with adetermination that the sequence of one or more inputs corresponds to arequest to replace the third complication, maintaining the firstcomplication and the second complication.
 3. The electronic device ofclaim 1, wherein: the first complication further includes a ninth metricrelated to data from the first application, the second complicationfurther includes a tenth metric related to data from the secondapplication, and the third complication further includes an eleventhmetric related to data from the third application.
 4. The electronicdevice of claim 1, wherein the first application is different than thesecond application, and wherein the third application is different thanthe first application and the second application.
 5. The electronicdevice of claim 1, the watch user interface further including aring-shaped area having a curved outer edge, the one or more programsfurther including instructions for: in accordance with the secondapplication corresponding to a respective application, displaying avisual characteristic at or around the ring-shaped area; and inaccordance with the second application corresponding to an applicationdifferent than the respective application, forgoing displaying thevisual characteristic at or around the ring-shaped area.
 6. Theelectronic device of claim 1, the one or more programs further includinginstructions for: displaying a second watch user interface, the secondwatch user interface including a fifth complication that includes lessthan two metrics related to data from the first application, wherein thefifth complication is the same size as the first complication.
 7. Theelectronic device of claim 6, wherein the fifth complication does notinclude a metric related to data from the first application.
 8. Theelectronic device of claim 1, wherein the analog clock face area has acurved outer edge and the first complication is a curved complicationhaving a visual feature that follows the outer edge of the analog clockface area.
 9. The electronic device of claim 1, wherein the firstapplication is a weather application, wherein the first metric and thesecond metric relate to data from the weather application, the firstmetric representing a current temperature, and the second metricrepresenting forecasted high and low temperatures.
 10. The electronicdevice of claim 1, wherein the first complication includes a visualrepresentation of one or more metrics, the visual representationincluding an indication of a value relative to a range of values. 11.The electronic device of claim 1, wherein the first complicationincludes a visual representation of one or more metrics, the visualrepresentation including a first affordance representing a simulation ofa first region of the Earth as illuminated by the Sun at a current time,the one or more programs further including instructions for: detecting asequence of one or more user inputs corresponding to a request to viewthe simulation of the Earth at a non-current time; and in response todetecting the sequence of one or more user inputs corresponding to arequest to view the simulation of the Earth at a non-current time,rotating the simulation of the Earth to reveal a second region of theEarth as illuminated by the Sun at the non-current time.
 12. Theelectronic device of claim 1, wherein the second complication and thethird complication are located outside of the analog clock face area.13. The electronic device of claim 1, wherein the watch user interfacefurther includes a bezel that at least partially surrounds the analogclock face area.
 14. The electronic device of claim 13, wherein thefirst complication is located between the bezel and a corner edge of thedisplay.
 15. A method, comprising: at an electronic device with adisplay, wherein the display has one or more corners: displaying a watchuser interface on the display, the watch user interface including: ananalog clock face area, the analog clock face area including an area ofthe display in which an hour hand and a minute hand rotate; a firstcomplication, wherein the first complication is located outside of theanalog clock face area and is in a first corner of the one or morecorners of the display, wherein the first complication includes atleast: a first metric related to data from a first application; a secondmetric related to data from the first application; a status bar thattracks an outer edge of the analog clock face area; and a value locatedbetween the status bar and the first corner of the display; a secondcomplication that includes at least a third metric related to data froma second application and a fourth metric related to data from the secondapplication; and a third complication that includes at least a fifthmetric related to data from a third application and a sixth metricrelated to data from the third application; detecting a sequence of oneor more inputs that corresponds to a request to add a fourthcomplication to the watch user interface, wherein the fourthcomplication includes at least a seventh metric related to data from afourth application and an eighth metric related to data from the fourthapplication; and in response to detecting the sequence of one or moreinputs: in accordance with a determination that the sequence of one ormore inputs corresponds to a request to replace the first complication,replacing the first complication outside of the analog clock face areawith the fourth complication; in accordance with a determination thatthe sequence of one or more inputs corresponds to a request to replacethe second complication, replacing the second complication with thefourth complication; and in accordance with a determination that thesequence of one or more inputs corresponds to a request to replace thethird complication, replacing the third complication with the fourthcomplication.
 16. The method of claim 15, further comprising: inresponse to detecting the sequence of one or more inputs: in accordancewith a determination that the sequence of one or more inputs correspondsto a request to replace the first complication, maintaining the secondcomplication and the third complication; in accordance with adetermination that the sequence of one or more inputs corresponds to arequest to replace the second complication, maintaining the firstcomplication and the third complication; and in accordance with adetermination that the sequence of one or more inputs corresponds to arequest to replace the third complication, maintaining the firstcomplication and the second complication.
 17. The method of claim 15,wherein: the first complication further includes a ninth metric relatedto data from the first application, the second complication furtherincludes a tenth metric related to data from the second application, andthe third complication further includes an eleventh metric related todata from the third application.
 18. The method of claim 15, wherein thefirst application is different than the second application, and whereinthe third application is different than the first application and thesecond application.
 19. The method of claim 15, the watch user interfacefurther including a ring-shaped area having a curved outer edge, themethod further comprising: in accordance with the second applicationcorresponding to a respective application, displaying a visualcharacteristic at or around the ring-shaped area; and in accordance withthe second application corresponding to an application different thanthe respective application, forgoing displaying the visualcharacteristic at or around the ring-shaped area.
 20. The method ofclaim 15, further comprising: displaying a second watch user interface,the second watch user interface including a fifth complication thatincludes less than two metrics related to data from the firstapplication, wherein the fifth complication is the same size as thefirst complication.
 21. The method of claim 20, wherein the fifthcomplication does not include a metric related to data from the firstapplication.
 22. The method of claim 15, wherein the analog clock facearea has a curved outer edge and the first complication is a curvedcomplication having a visual feature that follows the outer edge of theanalog clock face area.
 23. The method of claim 15, wherein the firstapplication is a weather application, wherein the first metric and thesecond metric relate to data from the weather application, the firstmetric representing a current temperature, and the second metricrepresenting forecasted high and low temperatures.
 24. The method ofclaim 15, wherein the first complication includes a visualrepresentation of one or more metrics, the visual representationincluding an indication of a value relative to a range of values. 25.The method of claim 15, wherein the first complication includes a visualrepresentation of one or more metrics, the visual representationincluding a first affordance representing a simulation of a first regionof the Earth as illuminated by the Sun at a current time, the methodfurther comprising: detecting a sequence of one or more user inputscorresponding to a request to view the simulation of the Earth at anon-current time; and in response to detecting the sequence of one ormore user inputs corresponding to a request to view the simulation ofthe Earth at a non-current time, rotating the simulation of the Earth toreveal a second region of the Earth as illuminated by the Sun at thenon-current time.
 26. The method of claim 15, wherein the secondcomplication and the third complication are located outside of theanalog clock face area.
 27. The method of claim 15, wherein the watchuser interface further includes a bezel that at least partiallysurrounds the analog clock face area.
 28. The method of claim 27,wherein the first complication is located between the bezel and a corneredge of the display.
 29. A non-transitory computer-readable storagemedium storing one or more programs configured to be executed by one ormore processors of an electronic device with a display, wherein thedisplay has one or more corners, the one or more programs includinginstructions for: displaying a watch user interface on the display, thewatch user interface including: an analog clock face area, the analogclock face area including an area of the display in which an hour handand a minute hand rotate; a first complication, wherein the firstcomplication is located outside of the analog clock face area and is ina first corner of the one or more corners of the display, wherein thefirst complication includes at least: a first metric related to datafrom a first application; a second metric related to data from the firstapplication; a status bar that tracks an outer edge of the analog clockface area; and a value located between the status bar and the firstcorner of the display; a second complication that includes at least athird metric related to data from a second application and a fourthmetric related to data from the second application; and a thirdcomplication that includes at least a fifth metric related to data froma third application and a sixth metric related to data from the thirdapplication; detecting a sequence of one or more inputs that correspondsto a request to add a fourth complication to the watch user interface,wherein the fourth complication includes at least a seventh metricrelated to data from a fourth application and an eighth metric relatedto data from the fourth application; and in response to detecting thesequence of one or more inputs: in accordance with a determination thatthe sequence of one or more inputs corresponds to a request to replacethe first complication, replacing the first complication outside of theanalog clock face area with the fourth complication; in accordance witha determination that the sequence of one or more inputs corresponds to arequest to replace the second complication, replacing the secondcomplication with the fourth complication; and in accordance with adetermination that the sequence of one or more inputs corresponds to arequest to replace the third complication, replacing the thirdcomplication with the fourth complication.
 30. The computer-readablestorage medium of claim 29, the one or more programs further includinginstructions for: in response to detecting the sequence of one or moreinputs: in accordance with a determination that the sequence of one ormore inputs corresponds to a request to replace the first complication,maintaining the second complication and the third complication; inaccordance with a determination that the sequence of one or more inputscorresponds to a request to replace the second complication, maintainingthe first complication and the third complication; and in accordancewith a determination that the sequence of one or more inputs correspondsto a request to replace the third complication, maintaining the firstcomplication and the second complication.
 31. The computer-readablestorage medium of claim 29, wherein: the first complication furtherincludes a ninth metric related to data from the first application, thesecond complication further includes a tenth metric related to data fromthe second application, and the third complication further includes aneleventh metric related to data from the third application.
 32. Thecomputer-readable storage medium of claim 29, wherein the firstapplication is different than the second application, and wherein thethird application is different than the first application and the secondapplication.
 33. The computer-readable storage medium of claim 29, thewatch user interface further including a ring-shaped area having acurved outer edge, the one or more programs further includinginstructions for: in accordance with the second applicationcorresponding to a respective application, displaying a visualcharacteristic at or around the ring-shaped area; and in accordance withthe second application corresponding to an application different thanthe respective application, forgoing displaying the visualcharacteristic at or around the ring-shaped area.
 34. Thecomputer-readable storage medium of claim 29, the one or more programsfurther including instructions for: displaying a second watch userinterface, the second watch user interface including a fifthcomplication that includes less than two metrics related to data fromthe first application, wherein the fifth complication is the same sizeas the first complication.
 35. The computer-readable storage medium ofclaim 34, wherein the fifth complication does not include a metricrelated to data from the first application.
 36. The computer-readablestorage medium of claim 29, wherein the analog clock face area has acurved outer edge and the first complication is a curved complicationhaving a visual feature that follows the outer edge of the analog clockface area.
 37. The computer-readable storage medium of claim 29, whereinthe first application is a weather application, wherein the first metricand the second metric relate to data from the weather application, thefirst metric representing a current temperature, and the second metricrepresenting forecasted high and low temperatures.
 38. Thecomputer-readable storage medium of claim 29, wherein the firstcomplication includes a visual representation of one or more metrics,the visual representation including an indication of a value relative toa range of values.
 39. The computer-readable storage medium of claim 29,wherein the first complication includes a visual representation of oneor more metrics, the visual representation including a first affordancerepresenting a simulation of a first region of the Earth as illuminatedby the Sun at a current time, the one or more programs further includinginstructions for: detecting a sequence of one or more user inputscorresponding to a request to view the simulation of the Earth at anon-current time; and in response to detecting the sequence of one ormore user inputs corresponding to a request to view the simulation ofthe Earth at a non-current time, rotating the simulation of the Earth toreveal a second region of the Earth as illuminated by the Sun at thenon-current time.
 40. The computer-readable storage medium of claim 29,wherein the second complication and the third complication are locatedoutside of the analog clock face area.
 41. The computer-readable storagemedium of claim 29, wherein the watch user interface further includes abezel that at least partially surrounds the analog clock face area. 42.The computer-readable storage medium of claim 41, wherein the firstcomplication is located between the bezel and a corner edge of thedisplay.